Data Forwarding and ND Resolution Implementation Pitfalls
draft-wbeebee-nd-implementation-pitfalls-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hemant Singh , Wes Beebee | ||
| Last updated | 2007-07-23 | ||
| 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
RFC 2461 [ND] describes host data forwarding and address resolution. However, nine years after the ND protocol became an RFC, IPv6 hosts still do not fully comply with RFC 2461 [ND]. In particular, hosts incorrectly implement on- vs. off-link data forwarding. This document clarifies host behavior and associated router behavior to define explicitly address resolution and data forwarding models. The set of new requirements beyond what has been specified in RFC 2461 [ND] and RFC 2462 [ADDRCONF] is restricted to clarifications deemed necessary to facilitate correct implementation. The intention of this document is to incorporate normative changes into draft-ietf-ipv6-rfc2461bis-11 [NDbis] and draft-ietf-ipv6-rfc2462bis-08 [ADDRCONFbis]. After this has been accomplished, this document will be on track to become an Informational RFC. Following the same model as RFC 2525 [TCPProb], a section of this document collects known IPv6 ND implementation problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)