Get the latest tech news
The "simple" 38 step journey to getting an RFC
Internet is built on the mutual understanding of network protocols and practices, and most of those protocols are defined using Request For Comments (RFC) or Best Common Practices (BCP) documents. The generally accepted source for modern day RFCs is the Internet Engineering Task Force (IETF), the term RFC has been hijacked by several different companies for their own uses.
By the end, there were 3 co-authors on our document, Job Snijders(who was the 1st author), Me, and Yingzhen Qu(who came in later in the process, but helped enormously with understanding in how to “patch” parts of the complicated language around the area we were working on) Assuming all approvals happen, the gears inside the IETF will turn and an email will go out on ietf-announce@ietf.org to announce a new RFC being published, bots will post things, archives will be updated, and the planet will continue orbiting the sun. But having also been on the implementing side of RFCs I don’t necessarily find them the easiest documents to grasp, I will more often reach for a Wireshark dissector if available before I go and read the RFC for the protocol I am looking at.
Or read this on Hacker News