Dual-stack clients and merging of data from DHCPv4 and DHCPv6
draft-ietf-dhc-dual-stack-merge-01
| Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stig Venaas , Tim Chown | ||
| Last updated | 2005-10-26 | ||
| 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
A node may have support for communications using both IPv4 and IPv6 protocols. Such a node may wish to obtain both IPv4 and IPv6 configuration settings via the Dynamic Host Configuration Protocol (DHCP). This can be done by using the IPv4 and the IPv6 DHC protocols respectively. This document considers mechanisms that allow such a node to make use of the configuration data from both protocols to obtain the desired common configuration.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)