IPv6 destination option header clarification
draft-dupont-destoptupd-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Francis Dupont | ||
| Last updated | 2001-11-15 | ||
| 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
The IPv6 specification [1] defines a header chain with two kinds of headers, non-terminal and terminal. Two non-terminal headers can carry options and one is very specialized for hop-by-hop processing so the destination option header is used for many purposes, including some not considered in [1] like mobility [2].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)