RFC 7112: Implications of Oversized IPv6 Header Chains
In plain English — editorial summary, not part of the RFC
The IPv6 specification allows IPv6 Header Chains of an arbitrary size. The specification also allows options that can, in turn, extend each of the headers. In those scenarios in which the IPv6 Header Chain or options are unusually long and packets are fragmented, or scenarios in which the fragment size is very small, the First Fragment of a packet may fail to include the entire IPv6 Header Chain. This document discusses the interoperability and security problems of such traffic, and updates RFC 2460 such that the First Fragment of a packet is required to contain the entire IPv6 Header Chain.
Document record
- Document ID
- RFC7112
- Published
- January 2014
- Authors
- F. Gont; V. Manral; R. Bonica
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 2460
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7098Using the IPv6 Flow Label for Load Balancing in Server FarmsCurrent
January 2014
- RFC 7136Significance of IPv6 Interface IdentifiersCurrent
February 2014
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 7083Modification to Default Values of SOL_MAX_RT and INF_MAX_RTObsoleted
November 2013
- RFC 7078Distributing Address Selection Policy Using DHCPv6Current
January 2014
- RFC 7077Update Notifications for Proxy Mobile IPv6Current
November 2013
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 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?