Standardizing IPv6 Extension Header Definition
draft-bhatia-6man-update-ipv6-ext-hdr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Manav Bhatia | ||
| Last updated | 2010-09-26 | ||
| 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
In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. There are a small number of such extension headers, each identified by a distinct Next Header value. However, it presents no backward compatible way for incrementally introducing new IPv6 extension headers inside the network. Additionally since there is no standard format for extension headers, it becomes impossible for intermediaries that want to deep inspect the packet to parse an incoming packet which carries an extension header that it does not recognize. This document attempts to standardize the IPv6 extension header format to fix these issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)