RFC 7120: Early IANA Allocation of Standards Track Code Points
In plain English — editorial summary, not part of the RFC
This memo describes the process for early allocation of code points by IANA from registries for which "Specification Required", "RFC Required", "IETF Review", or "Standards Action" policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC, which would normally trigger code point allocation. The procedures in this document are intended to apply only to IETF Stream documents.
Document record
- Document ID
- RFC7120
- Published
- January 2014
- Authors
- M. Cotton
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- BCP100
- Obsoletes:
- RFC 4020
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3216SMIng ObjectivesCurrent
December 2001
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 7199Location Configuration Extensions for Policy ManagementCurrent
April 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 6813The Network Endpoint Assessment (NEA) Asokan Attack AnalysisCurrent
December 2012
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
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?