RFC 7045: Transmission and Processing of IPv6 Extension Headers
In plain English — editorial summary, not part of the RFC
Various IPv6 extension headers have been standardised since the IPv6 standard was first published. This document updates RFC 2460 to clarify how intermediate nodes should deal with such extension headers and with any that are defined in the future. It also specifies how extension headers should be registered by IANA, with a corresponding minor update to RFC 2780.
Document record
- Document ID
- RFC7045
- Published
- December 2013
- Authors
- B. Carpenter; S. Jiang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
- RFC 7040Public IPv4-over-IPv6 Access NetworkCurrent
November 2013
- RFC 7039Source Address Validation Improvement (SAVI) FrameworkCurrent
October 2013
- RFC 7037RADIUS Option for the DHCPv6 Relay AgentCurrent
October 2013
- RFC 7031DHCPv6 Failover RequirementsCurrent
September 2013
- RFC 7028Multicast Mobility Routing Optimizations for Proxy Mobile IPv6Current
September 2013
- RFC 7077Update Notifications for Proxy Mobile IPv6Current
November 2013
- RFC 7078Distributing Address Selection Policy Using DHCPv6Current
January 2014
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?