IPv6 Extension Headers Reserved Space
draft-pfeifer-6man-exthdr-res-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hagen Paul Pfeifer | ||
| Last updated | 2012-03-26 (Latest revision 2011-09-11) | ||
| 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
This document specify a mechanism to allow IPv6 stack implementation to parse upcoming IPv6 extension header by reserving a small range of protocol numbers for well defined IPv6 extension headers. IPv6 stack implementors can code these range into their network stack a priori. These reserved range provide an guarantee that a given next header is a well formed extension header and not a next layer protocol. Operators, companies, vendors et cetera are in the ability to deploy and test not standardized extension headers without modifying every middle box parsing the complete extension header chain in between.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)