Storing tunnel endpoint in the DNS
draft-durand-ngtrans-tunnel-endpoint-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Alain Durand | ||
Last updated | 2000-11-30 | ||
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
Tunnels in various forms (IPv6 in IPv4, IPv4 in IPv6,...) are key elements in many IPv6 transition scenarios. Tunnels can be either dynamically managed or manually configured. In this later case, managing tunnel endpoint is critical. This document describe a simple mechanism to store and retrieve those endpoint in the DNS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)