IPv6 Stateless Fragmentation Identification Options
draft-andrews-6man-fragopt-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 2014-02-06 (Latest revision 2013-08-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Fragmented IPv6 packets are often dropped because there is no way to identify whether a fragment matches a otherwise permitted packet as the L4 header information is not available on all the fragments. The document defines hop-by-hop options that can be used to supply the missing information in non initial fragments.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)