Search RFCs
RFC 7112
Implications of Oversized IPv6 Header Chains,January 2014
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 2460
- Authors:
- F. Gont
V. Manral
R. Bonica - Stream:
- IETF
- Source:
- 6man (int)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7112
Discuss this RFC: Send questions or comments to the mailing listipv6@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7112
Abstract
The IPv6 specification allows IPv6 Header Chains of an arbitrarysize. The specification also allows options that can, in turn,extend each of the headers. In those scenarios in which the IPv6Header Chain or options are unusually long and packets arefragmented, or scenarios in which the fragment size is very small,the First Fragment of a packet may fail to include the entire IPv6Header Chain. This document discusses the interoperability andsecurity problems of such traffic, and updates RFC 2460 such that theFirst Fragment of a packet is required to contain the entire IPv6Header Chain.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.