Security and Interoperability Implications of Oversized IPv6 Header Chains

The information below is for an old version of the document
Document Type Expired Internet-Draft (6man WG)
Authors Fernando Gont  , Vishwas Manral 
Last updated 2013-05-09 (latest revision 2012-11-05)
Replaces draft-gont-6man-oversized-header-chain
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.)