I’ve been reading some informational RFCs lately that are, frankly, a pile of bullsh*t. At what point do we start to tell vendors to stop publishing vapid and empty RFCs that promote their own agendas or support their marketing goals ? Should we allow clearly pointless RFC to actually pass through the IETF gullet ? I propose that we mark pointless RFCs clearly in the future.
Time to resurrect this RFC for IETF RFC for certain types of RFCs. You know who you are.
This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). The SOB process is similar to that of the normal standards track. The SOB is submitted to the IAB, the IRSG, the IESG, the SOB Editor (Morpheus), and the Academie Francais for review, analysis, reproduction in triplicate, translation into ASN.1, and distribution to Internet insomniacs. However, once everyone has approved the document by falling asleep over it, the process ends and the document is discarded. The resulting vacuum is viewed as having the technical approval of the IETF, but it is not, and cannot become, an official Internet Standard.
via RFC 1438 – Internet Engineering Task Force Statements Of Boredom (SOBs).
