Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 3315,RFC 3633,RFC 3736,RFC 4242,RFC 7083,RFC 7283,RFC 7550

Obsoleted by:

RFC 9915

Authors:

T. Mrugalski
M. Siodelski
B. Volz
A. Yourtchenko
M. Richardson
S. Jiang
T. Lemon
T. Winters

Stream:

IETF

Source:

dhc (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8415

Discuss this RFC: Send questions or comments to the mailing listdhcwg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8415

Abstract

This document describes the Dynamic Host Configuration Protocol forIPv6 (DHCPv6): an extensible mechanism for configuring nodes withnetwork configuration parameters, IP addresses, and prefixes.Parameters can be provided statelessly, or in combination withstateful assignment of one or more IPv6 addresses and/or IPv6prefixes. DHCPv6 can operate either in place of or in addition tostateless address autoconfiguration (SLAAC).

This document updates the text from RFC 3315 (the original DHCPv6specification) and incorporates prefix delegation (RFC 3633),stateless DHCPv6 (RFC 3736), an option to specify an upper bound forhow long a client should wait before refreshing information (RFC4242), a mechanism for throttling DHCPv6 clients when DHCPv6 serviceis not available (RFC 7083), and relay agent handling of unknownmessages (RFC 7283). In addition, this document clarifies theinteractions between models of operation (RFC 7550). As such, thisdocument obsoletes RFC 3315, RFC 3633, RFC 3736, RFC 4242, RFC 7083,RFC 7283, and RFC 7550.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.