Configured Tunnel End Point Option for DHCPv6
draft-ietf-dhc-dhcpv6-ctep-opt-02
| Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Soohong Daniel Park , a Vijayabhaskar | ||
| Last updated | 2005-10-25 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
For the newly deployed IPv6 networks to interoperate with vastly deployed IPv4 networks, various transition mechanisms had been proposed. One such mechanism is configured tunnels. This document provides a tunnel discovery mechanism by which the DHCPv6 servers can provide information about the available configured tunnel end points to reach the IPv6 nodes which are separated by IPv4 networks.
Authors
Soohong Daniel Park
a Vijayabhaskar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)