Transmission of IPv6 Extension Headers
draft-carpenter-6man-ext-transmit-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian E. Carpenter , Sheng Jiang | ||
| Last updated | 2013-05-10 (Latest revision 2013-02-21) | ||
| Replaced by | draft-ietf-6man-ext-transmit | ||
| 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-ext-transmit | |
| 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
Various IPv6 extension headers have been defined since the IPv6 standard was first published. This document updates RFC 2460 to clarify how intermediate nodes should deal with such extension headers and with any that are defined in future. It also specifies how extension headers should be registered by IANA, with a corresponding minor update to RFC 2780.
Authors
Brian E. Carpenter
Sheng Jiang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)