Security and Interoperability Implications of Oversized IPv6 Header Chains
draft-gont-6man-oversized-header-chain-02

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2012-12-10 (latest revision 2012-06-13)
Replaced by draft-ietf-6man-oversized-header-chain
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-6man-oversized-header-chain
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-gont-6man-oversized-header-chain-02.txt

Abstract

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.

Authors

Fernando Gont (fgont@si6networks.com)
Vishwas Manral (vishwas.manral@hp.com)

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