Analysis of IPv6 Tunnel End-point Discovery Mechanisms
draft-palet-v6ops-tun-auto-disc-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jordi Palet Martinez , Miguel Diaz | ||
| Last updated | 2005-01-24 (Latest revision 2004-10-26) | ||
| RFC stream | (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
To be able to automate setting up IPv6-in-IPv4 tunnels, it is important to be able to automatically determine the tunnel end-point for the tunneling mechanism. This memo presents a short analysis and conclusions on the different approaches for discovering the IPv6 tunnel endpoint on a node.
Authors
Jordi Palet Martinez
Miguel Diaz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)