IPv6 Neighbor Discovery Extensions for Inverse Discovery Specification
draft-conta-ipv6-nd_ext_ind-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alex Conta | ||
| Last updated | 1997-08-04 | ||
| 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 memo describes a mechanism that can be seen as an extension to the IPv6 Neighbor Discovery. It allows a node to solicit and be advertized an IPv6 address corresponding to a given link-layer address. Because the known parameter is the link layer address, the mechanism is called Inverse Neighbor Discovery. It specifically applies to Frame Relay nodes that may have a Data Link Connection Identifier (DLCI), the Frame Relay equivalent of a link-layer address, associated with an established Permanent Virtual Circuit (PVC), but do not know the IPv6 address of the node at the other end of the circuit. It may also apply to other networks with similar behavior.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)