RFC 8436: Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) Registry
In plain English — editorial summary, not part of the RFC
The Differentiated Services (Diffserv) architecture specifies use of the DS field in the IPv4 and IPv6 packet headers to carry one of 64 distinct differentiated services field codepoint (DSCP) values. The Internet Assigned Numbers Authority (IANA) maintains a registry of assigned DSCP values. This update to RFC 2474 changes the IANA registration policy for Pool 3 of the registry (i.e., DSCP values of the form xxxx01) to Standards Action, i.e., values are assigned through a Standards Track or Best Current Practice RFC. The update also removes permission for experimental and local use of the codepoints that form Pool 3 of the DSCP registry; Pool 2 Codepoints (i.e., DSCP values of the form xxxx11) remain available for these purposes.
Document record
- Document ID
- RFC8436
- Published
- August 2018
- Authors
- G. Fairhurst
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 2474
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 7657Differentiated Services (Diffserv) and Real-Time CommunicationCurrent
November 2015
- RFC 8100Diffserv-Interconnection Classes and PracticeCurrent
March 2017
- RFC 8837Differentiated Services Code Point (DSCP) Packet Markings for WebRTC QoSCurrent
January 2021
- RFC 9435Considerations for Assigning a New Recommended Differentiated Services Code Point (DSCP)Current
July 2023
- RFC 9956A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated ServicesCurrent
May 2026
- RFC 5129Explicit Congestion Marking in MPLSUpdated
January 2008
- RFC 4594Configuration Guidelines for DiffServ Service ClassesUpdated
August 2006
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?