IPv6 Inverse Neighbor Discovery for IPv6 and IPv4 Tunnels
draft-conta-ipv6-inv-nd-tun-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Alex Conta | ||
| Last updated | 1997-07-30 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-conta-ipv6-inv-nd-tun-00.txt
Abstract
This memo describes an extension mechanism to the IPv6 Neighbor Discovery and IPv6 Inverse Neighbor Discovery [IND] that applies to IPv6 and IPv4 tunnels. The mechanism can be used to advertise the parameters of a tunnel to its exit point node, and to create a reverse tunnel path between the exit point and entry point nodes of a unidirectional tunnel. If such a bidirectional tunnel already exists, the mechanism can be used to learn the IPv6 address of the tunnel pseudointerface of the exit-point node, as well as the reverse tunnel path parameters.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)