<referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bcp9"> <reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026"> <front> <title>The Internet Standards Process -- Revision 3</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="October" year="1996"/> <abstract> <t>This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="2026"/> <seriesInfo name="DOI" value="10.17487/RFC2026"/> </reference> <reference anchor="RFC5657" target="https://www.rfc-editor.org/info/rfc5657"> <front> <title>Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard</title> <author fullname="L. Dusseault" initials="L." surname="Dusseault"/> <author fullname="R. Sparks" initials="R." surname="Sparks"/> <date month="September" year="2009"/> <abstract> <t>Advancing a protocol to Draft Standard requires documentation of the interoperation and implementation of the protocol. Historic reports have varied widely in form and level of content and there is little guidance available to new report preparers. This document updates the existing processes and provides more detail on what is appropriate in an interoperability and implementation report. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="5657"/> <seriesInfo name="DOI" value="10.17487/RFC5657"/> </reference> <reference anchor="RFC6410" target="https://www.rfc-editor.org/info/rfc6410"> <front> <title>Reducing the Standards Track to Two Maturity Levels</title> <author fullname="R. Housley" initials="R." surname="Housley"/> <author fullname="D. Crocker" initials="D." surname="Crocker"/> <author fullname="E. Burger" initials="E." surname="Burger"/> <date month="October" year="2011"/> <abstract> <t>This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="6410"/> <seriesInfo name="DOI" value="10.17487/RFC6410"/> </reference> <reference anchor="RFC7100" target="https://www.rfc-editor.org/info/rfc7100"> <front> <title>Retirement of the "Internet Official Protocol Standards" Summary Document</title> <author fullname="P. Resnick" initials="P." surname="Resnick"/> <date month="December" year="2013"/> <abstract> <t>This document updates RFC 2026 to no longer use STD 1 as a summary of "Internet Official Protocol Standards". It obsoletes RFC 5000 and requests the IESG to move RFC 5000 (and therefore STD 1) to Historic status.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7100"/> <seriesInfo name="DOI" value="10.17487/RFC7100"/> </reference> <reference anchor="RFC7127" target="https://www.rfc-editor.org/info/rfc7127"> <front> <title>Characterization of Proposed Standards</title> <author fullname="O. Kolkman" initials="O." surname="Kolkman"/> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <author fullname="S. Turner" initials="S." surname="Turner"/> <date month="January" year="2014"/> <abstract> <t>RFC 2026 describes the review performed by the Internet Engineering Steering Group (IESG) on IETF Proposed Standard RFCs and characterizes the maturity level of those documents. This document updates RFC 2026 by providing a current and more accurate characterization of Proposed Standards.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7127"/> <seriesInfo name="DOI" value="10.17487/RFC7127"/> </reference> <reference anchor="RFC7475" target="https://www.rfc-editor.org/info/rfc7475"> <front> <title>Increasing the Number of Area Directors in an IETF Area</title> <author fullname="S. Dawkins" initials="S." surname="Dawkins"/> <date month="March" year="2015"/> <abstract> <t>This document removes a limit on the number of Area Directors who manage an Area in the definition of "IETF Area". This document updates RFC 2026 (BCP 9) and RFC 2418 (BCP 25).</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7475"/> <seriesInfo name="DOI" value="10.17487/RFC7475"/> </reference> <reference anchor="RFC8789" target="https://www.rfc-editor.org/info/rfc8789"> <front> <title>IETF Stream Documents Require IETF Rough Consensus</title> <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/> <author fullname="E. Rescorla" initials="E." role="editor" surname="Rescorla"/> <date month="June" year="2020"/> <abstract> <t>This document requires that the IETF never publish any IETF Stream RFCs without IETF rough consensus. This updates RFC 2026.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="8789"/> <seriesInfo name="DOI" value="10.17487/RFC8789"/> </reference> <reference anchor="RFC9282" target="https://www.rfc-editor.org/info/rfc9282"> <front> <title>Responsibility Change for the RFC Series</title> <author fullname="B. Rosen" initials="B." surname="Rosen"/> <date month="June" year="2022"/> <abstract> <t>In RFC 9280, responsibility for the RFC Series moved to the RFC Series Working Group and the RFC Series Approval Board. It is no longer the responsibility of the RFC Editor, and the role of the IAB in the RFC Series is altered. Accordingly, in Section 2.1 of RFC 2026, the sentence "RFC publication is the direct responsibility of the RFC Editor, under the general direction of the IAB" is deleted.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="9282"/> <seriesInfo name="DOI" value="10.17487/RFC9282"/> </reference> </referencegroup>