RFC 7112

Implications of Oversized IPv6 Header Chains, January 2014

File formats:
icon for text file icon for PDF icon for HTML
RFC 2460
F. Gont
V. Manral
R. Bonica
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 list ipv6@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7112


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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search