DHCPv4 over IPv6 Transport
draft-ietf-dhc-dhcpv4-over-ipv6-06
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Yong Cui , Peng Wu , Jianping Wu , Ted Lemon | ||
Last updated | 2013-09-21 (Latest revision 2013-03-20) | ||
Replaces | draft-cui-dhc-dhcpv4-over-ipv6 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
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
In IPv6 networks, there remains a need to provide IPv4 service for some residual devices. This document describes a mechanism for allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6 transport. It is done by putting a special relay agent function (Client Relay Agent) on the client side, as well as extending the behavior of the server; in the case where DHCP server only supports IPv4 transport, a relay agent is extended to support IPv6 transport (IPv6-Transport Relay Agent) and relay DHCP traffic for the server, with a new Relay Agent Information sub-option added to carry the IPv6 address of the Client Relay Agent.
Authors
Yong Cui
Peng Wu
Jianping Wu
Ted Lemon
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)