Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 8
- Abstract
- 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.
- Publication Date
- 2005-05-01
- Status Note
- Informational
- DOI
10.17487/RFC4076- Link
- https://doi.org/10.17487/RFC4076
- Author(s)
- Tim ChownStig Venaasa Vijayabhaskar
- Keyword(s)
- IP, SLAAC
Latest version of IETF RFC 4076
Document Versions — IETF RFC 4076
-
▶ IETF RFC 4076 (2005-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2461 [Superseded*]
- IETF RFC 2462 [Superseded*]
- IETF RFC 3315 [Superseded*]
- IETF RFC 3736 [Superseded*]
Bibliographic Reference(s)
- Baker, F., Lear, E. and R. Droms, "Procedures for Renumbering an IPv6 Network without a Flag Day", Work in Progress, July 2004. EXTERNAL
- Choi, J., "Goals of Detecting Network Attachment (DNA) in IPv6" , Work in Progress, October 2004. EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4076.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4076, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6). Available at https://doi.org/10.17487/RFC4076
Snippet:
IETF RFC 4076, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6). Available at https://doi.org/10.17487/RFC4076
HTML (ISO 690 compliant)
Preview:
IETF RFC 4076, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6). Available at https://doi.org/10.17487/RFC4076
Snippet:
<span class="citation"><cite>IETF RFC 4076</cite>, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6). Available at <a href="https://doi.org/10.17487/RFC4076" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4076</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4076, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
doi: 10.17487/RFC4076
url: https://doi.org/10.17487/RFC4076
doi: 10.17487/RFC4076
url: https://doi.org/10.17487/RFC4076
Snippet:
<li> <cite id="bib-rfc4076">IETF RFC 4076</cite>, Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6) <span class="doi">10.17487/RFC4076</span> </li>
Referenced By
- IETF RFC 4242 [Superseded*]
- IETF RFC 4339 [Active*]
- IETF RFC 5887 [Active*]