Skip to main content

Security and Interoperability Implications of Oversized IPv6 Header Chains

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Fernando Gont , Vishwas Manral
Last updated 2012-12-10 (Latest revision 2012-06-13)
Replaced by draft-ietf-6man-oversized-header-chain
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-6man-oversized-header-chain
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The IPv6 specification allows IPv6 header chains of an arbitrary size. The specification also allows options which 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.


Fernando Gont
Vishwas Manral

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)