RFC 7280: IANA Guidance for Managing the Unidirectional Lightweight Encapsulation (ULE) Next-Header Registry
In plain English — editorial summary, not part of the RFC
This document updates RFC 4326 to clarify and update the allocation rules for the Unidirectional Lightweight Encapsulation (ULE) Next- Header registry. This registry is used by ULE and Generic Stream Encapsulation (GSE) to record the code points of Extension Headers and protocols supported by these encapsulation protocols.
Document record
- Document ID
- RFC7280
- Published
- June 2014
- Authors
- G. Fairhurst
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 4326
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7319IANA Considerations for Connectivity Fault Management (CFM) Code PointsCurrent
July 2014
- RFC 7013Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information ElementsCurrent
September 2013
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 6918Formally Deprecating Some ICMPv4 Message TypesCurrent
April 2013
- RFC 6491Resource Public Key Infrastructure (RPKI) Objects Issued by IANACurrent
February 2012
- RFC 6335Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number RegistryCurrent
August 2011
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
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?