IPv6 Universal Extension Header
draft-gont-6man-ipv6-universal-extension-header-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Fernando Gont , Will (Shucheng) LIU , Suresh Krishnan , Hagen Paul Pfeifer | ||
| Last updated | 2014-10-10 (Latest revision 2014-04-08) | ||
| RFC stream | (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 analyzes a problem in the Uniform Format for IPv6 Extension Headers specified in RFC 6564, which results in nodes not being able to process an IPv6 Header Chain if it contains an unrecognized IPv6 Extension Header that follows the aforementioned Uniform Format. It analyzes the implications of the aforementioned problem, and discusses a number of possible solutions, including the specification of a new IPv6 Extension Header - the Universal Extension Header - that overcomes the aforementioned issues.
Authors
Fernando Gont
Will (Shucheng) LIU
Suresh Krishnan
Hagen Paul Pfeifer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)