IPv6 Type 0 Routing Header Processing
draft-savola-ipv6-rtheader-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pekka Savola , George Neville-Neil | ||
| Last updated | 2007-05-08 | ||
| 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
IPv6 type 0 routing header has been demonstrated to be a very powerful mechanism as currently specified in RFC 2460. This memo refers to description of problems associated with the use of type 0 routing header and specifies that implementations should disable type 0 routing header processing by default.
Authors
Pekka Savola
George Neville-Neil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)