Configured Tunnel End Point Option for DHCPv6
draft-daniel-dhc-dhcpv6-ctep-opt-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Soohong Daniel Park | ||
| Last updated | 2003-12-18 | ||
| 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
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 mechanism by which the DHCPv6 servers can provide information about the various configured tunnel end points to reach the IPv6 nodes which are separated by IPv4 networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)