Issues with overlapping IPv6 fragments
draft-krishnan-6man-overlap-fragment-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Suresh Krishnan | ||
| Last updated | 2008-10-27 (Latest revision 2008-07-14) | ||
| Replaced by | draft-ietf-6man-overlap-fragment | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-overlap-fragment | |
| 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:
Abstract
The fragmentation and reassembly algorithm specified in the base IPv6 specification allows fragments to overlap. This document demonstrates the security issues with allowing overlapping fragments and updates the IPv6 specification to explicitly forbid overlapping fragments.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)