RFC 7127: Characterization of Proposed Standards
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7127
- Published
- January 2014
- Authors
- O. Kolkman; S. Bradner; S. Turner
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- BCP9
- Updates:
- RFC 2026
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5657Guidance on Interoperation and Implementation Reports for Advancement to Draft StandardCurrent
September 2009
- RFC 4188Definitions of Managed Objects for BridgesCurrent
September 2005
- RFC 2120Managing the X.500 Root Naming ContextCurrent
March 1997
- RFC 2119Key words for use in RFCs to Indicate Requirement LevelsUpdated
March 1997
- RFC 1493Definitions of Managed Objects for BridgesObsoleted
July 1993
- RFC 1490Multiprotocol Interconnect over Frame RelayObsoleted
July 1993
- RFC 1294Multiprotocol Interconnect over Frame RelayObsoleted
January 1992
- RFC 1293Inverse Address Resolution ProtocolObsoleted
January 1992
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?