> Not really. RFCs in the Informational category don't need consensus. They don't, but they also need to not conflict with any IETF activity: "4.2.3 Procedur

> Not really. RFCs in the Informational category don't need consensus. They don't, but they also need to not conflict with any IETF activity: "4.2.3 Procedures for Experimental and Informational RFCs [...] To ensure that the non-standards track Experimental and Informational designations are not misused to circumvent the Internet Standards Process, the IESG and the RFC Editor have agreed that the RFC Editor will refer to the IESG any document submitted for Experimental or Informational publication which, in the opinion of the RFC Editor, may be related to work being done, or expected to be done, within the IETF community." [https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2.3 https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2.3] Apart from that, it's unclear to me what the document is actually trying to do [cf. my comment in https://news.ycombinator.com/item?id=23769617 https://news.ycombinator.com/item?id=23769617]