3 ms·
As a note this is a draft informational RFC from one member, albeit a cool one :). It is not an overall stance, consensus, or best practices of the IETF. From R
by zamadatix 4y ago
As a note this is a draft informational RFC from one member, albeit a cool one :). It is not an overall stance, consensus, or best practices of the IETF. From RFC 2026:
> An "Informational" specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation.
A lot of people associate "RFC" with standards track RFCs so I felt this could cause some confusion.
- AlbertCory 4y agoEven a "draft" RFC like this one goes through an extensive review process. My own RFC (1697) never advanced beyond Draft stage, but it was still the product of an open process attended by all the major RDBMS vendors. The stages of "standardness" have been there since the 1980s. Many important RFCs have never gone beyond Draft.
- zamadatix 4y agoThe main note here is more this is an informational RFC, which happens to still be draft, unlike e.g. RFC 1697 which is standards track. For non-standards track the review process can be extremely light in comparison since you're not making any claim there is consensus or official recommendation. For informational you pretty much submit it and as long as the editor agrees it's submitted to the correct category, somewhat reasonable, and formatted appropriately then it will be published. See section 4.2.3 of the aforementioned RFC 2026 (which itself is Best Current Practices, an entirely different group of documents!) for the specific details. As an example of an equivilant informational draft I was involved in https://www.ietf.org/archive/id/draft-lapuh-spb-deployment-03.txt https://www.ietf.org/archive/id/draft-lapuh-spb-deployment-0... I can say it reached this stage with basically no review. If you wanted to have an equivalently published document on centralisation stating the exact opposite of everything this one does you could have it up by the end of the month without worrying about review.
- AlbertCory 4y agoThanks, 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.
- berkeleyjunk 4y agoNot to be pedantic but this is not an RFC (yet). It is only a draft and should hopefully become an RFC in the future. The basic difference is that a draft is versioned and can change in content but an RFC is stable. Also, RFCs are certainly not only standards track. There is a mix of types including Informational, Experimental and Standards track RFCs.
- zamadatix 4y agoI agree 100% it's not yet an true "RFC". "Internet Draft" would be the proper terminology but I couldn't figure how to cleanly work that explanation in one swoop without distracting from the main point that it's just informational and instead fudged "draft informational RFC". There was no claim that RFCs must be standards track, this is actually a false relation the last line explicitly calls out people for having. Maybe it should have been made even clearer this is a false assumption without relying on context. I wonder if RFC 2026 is worthy of its own HN post. Just submitted :).