Renumbering Requirements for Stateless DHCPv6
draft-chown-dhc-stateless-dhcpv6-renumbering-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|---|---|---|
| Authors | Tim Chown , Stig Venaas , a Vijayabhaskar | |
| Last updated | 2003年11月20日 | |
| 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
IPv6 hosts using Stateless Address Autoconfiguration are able to automatically configure their IPv6 address and default router settings. However, further settings are not available. If such hosts wish to automatically configure their DNS, NTP or other specific settings the stateless variant of the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) could be used. This combination of Stateless Address Autoconfiguration and stateless DHCPv6 could be used quite commonly in IPv6 networks. However, hosts using such a combination currently have no means by which to be informed of changes in stateless DHCPv6 option settings, e.g. the addition of a new NTP server address, changes in DNS search paths, or full site renumbering. This document is presented as a problem statement from which a solution should be proposed in a subsequent document.
Authors
Tim Chown
Stig Venaas
a Vijayabhaskar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)