…ry 2016 2.33.2 . "consensus" Attribute Affects the generated boilerplate. See [ RFC5741 ] for more information. Allowed values: o "no" o "yes" 2.33.3 . "docName" Attribute For Internet-Drafts, this specifies the draft name (which appears below the title). A processor should give …

…entify the document as the product of the IRTF. The current text is defined in [RFC5741]. 3. Rules for Submission and Use of Material The goals of the IRTF Stream are based on a desire that research within the IRTF have broad impact and the publication rights should, in general, …

…ultation with the community, for ease of maintenance. This document obsoletes [ RFC5741 ]. The changes introduced by this memo should be implemented as soon as practically possible after the document has been approved for publication. . RFC Streams and Internet Standards Users of…

… IAB have separated their publication "streams" as described in RFC4844 ] and [ RFC5741 ]. This document was initiated after discussions in both the IESG and IAB, but is published as an IETF- stream consensus document, in order to ensure that it properly reflects the consensus of…

…pends on whether there was a consensus to publish (again, see Section 3.2.2 of [RFC5741]). The "consensus" attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: o "independent" and "IAB": none. o "IETF": mention…

…14 ]"). Inclusion of the URI to the STD or BCP info page (see Section 3.2.3 of [RFC5741] ) is recommended. The text should appear as follows: See RFC 1034 STD13 ]. For an STD or BCP that contains one RFC: STDXXX ] Last name, First initial., Ed. (if applicable), "RFC Title", Strea…

…pends on whether there was a consensus to publish (again, see Section 3.2.2 of [RFC5741]). The "consensus" attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: o "independent" and "IAB": none. o "IETF": mention…