RFC 4076: Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
IPv6 hosts using Stateless Address Autoconfiguration are able to configure their IPv6 address and default router settings automatically. However, further settings are not available. If these hosts wish to configure their DNS, NTP, or other specific settings automatically, 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 this 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, a change 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. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4076
- Published
- May 2005
- Authors
- T. Chown; S. Venaas; A. Vijayabhaskar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4087IP Tunnel MIBCurrent
June 2005
- RFC 4064Experimental Message, Extensions, and Error Codes for Mobile IPv4Current
May 2005
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4193Unique Local IPv6 Unicast AddressesCurrent
October 2005
- RFC 4242Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2005
- RFC 3879Deprecating Site Local AddressesCurrent
September 2004
- RFC 4292IP Forwarding Table MIBCurrent
April 2006
- RFC 3846Mobile IPv4 Extension for Carrying Network Access IdentifiersCurrent
June 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?