3 ms·
Thanks, I realized after saying that, that "Informational" RFCs are different from standards-track. That said, they say right at the top that this is Informati
by AlbertCory 4y ago
Thanks, I realized after saying that, that "Informational" RFCs are different from standards-track.
That said, they say right at the top that this is Informational, don't they?
Also, if you did try "an equivalently published document on centralisation stating the exact opposite" of the IETF position, I have a suspicion you'd run into some problems. Wouldn't you? At least some public statements that "that's just his opinion, man."
- zamadatix 4y agoThe main trouble would be you'd need to sell it as sounding reasonable so you'd actually have to have reasoning not just state the opposite for the heck of it. That said there is nothing wrong with conflicting informational RFCs, they are meant to share information with the community not to convey consensus so it's fine to have conflicting views as long as it sources from differing information. That said it's generally considered better for you and the other person try to come to a common understanding and share that information as one informational document.