Characterization of Proposed Standards
RFC 7127
Document | Type |
RFC - Best Current Practice
(January 2014; No errata)
Updates RFC 2026
Was draft-kolkman-proposed-standards-clarified (individual in gen area)
|
|
---|---|---|---|
Authors | Olaf Kolkman , Scott Bradner , Sean Turner | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jari Arkko | ||
IESG | IESG state | RFC 7127 (Best Current Practice) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Jari Arkko | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) O. Kolkman Request for Comments: 7127 NLnet Labs BCP: 9 S. Bradner Updates: 2026 Harvard University Category: Best Current Practice S. Turner ISSN: 2070-1721 IECA, Inc. January 2014 Characterization of Proposed Standards Abstract 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. Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7127. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Kolkman, et al. Best Current Practice [Page 1] RFC 7127 Characterization of Proposed Standards January 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IETF Review of Proposed Standards . . . . . . . . . . . . . . 2 3. Characterization of Specifications . . . . . . . . . . . . . 3 3.1. Characterization of IETF Proposed Standard Specifications 3 3.2. Characteristics of Internet Standards . . . . . . . . . . 4 4. Further Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 1. Introduction In the two decades after publication of RFC 2026 [RFC2026], the IETF has evolved its review processes of Proposed Standard RFCs, and thus Section 4.1.1 of RFC 2026 no longer accurately describes IETF Proposed Standards. This document only updates the characterization of Proposed Standards from Section 4.1.1 of RFC 2026 and does not speak to or alter the procedures for the maintenance of Standards Track documents from RFC 2026 and RFC 6410 [RFC6410]. For complete understanding of the requirements for standardization, those documents should be read in conjunction with this document. 2. IETF Review of Proposed Standards The entry-level maturity for the standards track is "Proposed Standard". A specific action by the IESG is required to move a specification onto the Standards Track at the "Proposed Standard" level. Initially it was intended that most IETF technical specifications would progress through a series of maturity stages starting with Proposed Standard, then progressing to Draft Standard, then finally to Internet Standard (see Section 6 of RFC 2026). For a number of reasons this progression is not common. Many Proposed Standards are actually deployed on the Internet and used extensively, as stable protocols. This proves the point that the community often deems it unnecessary to upgrade a specification to Internet Standard. Actual practice has been that full progression through the sequence of standards levels is typically quite rare, and most popular IETF protocols remain at Proposed Standard. Over time, the IETF has developed a more extensive review process. Kolkman, et al. Best Current Practice [Page 2] RFC 7127 Characterization of Proposed Standards January 2014 IETF Proposed Standards documents have been subject to open development and review by the Internet technical community, generally including a number of formal cross-discipline reviews and, specifically, a security review. This is further strengthened inShow full document text