Cite this BCP: TXTBCP 9 contains the following RFCs:
|RFC 2026, BCP 9||The Internet Standards Process -- Revision 3||S. Bradner||October 1996||Obsoletes RFC 1602, RFC 1871, Updated by RFC 3667, RFC 3668, RFC 3932, RFC 3978, RFC 3979, RFC 5378, RFC 5657, RFC 5742, RFC 6410, RFC 7100, RFC 7127, RFC 7475, RFC 8179, RFC 8789, RFC 9282, Errata||Best Current Practice|
|RFC 5657, BCP 9||Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard||L. Dusseault, R. Sparks||September 2009||Updates RFC 2026, Errata||Best Current Practice|
|RFC 6410, BCP 9||Reducing the Standards Track to Two Maturity Levels||R. Housley, D. Crocker, E. Burger||October 2011||Updates RFC 2026, Errata||Best Current Practice|
|RFC 7100, BCP 9||Retirement of the "Internet Official Protocol Standards" Summary Document||P. Resnick||December 2013||Obsoletes RFC 5000, Updates RFC 2026||Best Current Practice|
|RFC 7127, BCP 9||Characterization of Proposed Standards||O. Kolkman, S. Bradner, S. Turner||January 2014||Updates RFC 2026||Best Current Practice|
|RFC 7475, BCP 9||Increasing the Number of Area Directors in an IETF Area||S. Dawkins||March 2015||Updates RFC 2026, RFC 2418||Best Current Practice|
|RFC 8789, BCP 9||IETF Stream Documents Require IETF Rough Consensus||J. Halpern, Ed., E. Rescorla, Ed.||June 2020||Updates RFC 2026||Best Current Practice|
|RFC 9282, BCP 9||Responsibility Change for the RFC Series||B. Rosen||June 2022||Updates RFC 2026||Best Current Practice|
Abstract of RFC 2026
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.
Abstract of RFC 5657
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.
Abstract of RFC 6410
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.
Abstract of RFC 7100
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.
Abstract of RFC 7127
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.
Abstract of RFC 7475
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).
Abstract of RFC 8789
This document requires that the IETF never publish any IETF Stream RFCs without IETF rough consensus. This updates RFC 2026.
Abstract of RFC 9282
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.