Implications of Oversized IPv6 Header Chains
RFC 7112, “Implications of Oversized IPv6 Header Chains”, is a Proposed Standard document published in January 2014 by F. Gont, V. Manral, R. Bonica. It updates RFC 2460. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7112 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7111 URI Fragment Identifiers for the text/csv Media Type
- RFC 7113 Implementation Advice for IPv6 Router Advertisement Guard
- RFC 7110 Return Path Specified Label Switched Path Ping
- RFC 7114 Creation of a Registry for smime-type Parameter Values
- RFC 7109 Flow Bindings Initiated by Home Agents for Mobile IPv6
- RFC 7115 Origin Validation Operation Based on the Resource Public Key Infrastructure
- RFC 7108 A Summary of Various Mechanisms Deployed at L-Root for the Identification of Anycast Nodes
- RFC 7116 Licklider Transmission Protocol , Compressed Bundle Header Encoding , and Bundle Protocol IANA Registries