RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9915.
Current document in this lineage: RFC 9915 — Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 prefixes. DHCPv6 can operate either in place of or in addition to stateless address autoconfiguration (SLAAC). This document updates the text from RFC 3315 (the original DHCPv6 specification) and incorporates prefix delegation (RFC 3633), stateless DHCPv6 (RFC 3736), an option to specify an upper bound for how long a client should wait before refreshing information (RFC 4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service is not available (RFC 7083), and relay agent handling of unknown messages (RFC 7283). In addition, this document clarifies the interactions between models of operation (RFC 7550). As such, this document obsoletes RFC 3315, RFC 3633, RFC 3736, RFC 4242, RFC 7083, RFC 7283, and RFC 7550.
Document record
- Document ID
- RFC8415
- Published
- November 2018
- Authors
- T. Mrugalski; M. Siodelski; B. Volz; A. Yourtchenko; M. Richardson; S. Jiang; T. Lemon; T. Winters
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 154
- Also known as
- —
- Obsoleted by:
- RFC 9915
Topics
Standards lineage
This document is one revision in a chain of 9 RFCs, each formally replacing the one before it.
- RFC 3315 (2003)
- RFC 3633 (2003)
- RFC 3736 (2004)
- RFC 4242 (2005)
- RFC 7083 (2013)
- RFC 7283 (2014)
- RFC 7550 (2015)
- RFC 8415 (2018)
- RFC 9915 (2026) ✓
Read the full history of Dynamic Host Configuration Protocol for IPv6 (DHCPv6) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 8801Discovering Provisioning Domain Names and DataCurrent
July 2020
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 9686Registering Self-Generated IPv6 Addresses Using DHCPv6Current
December 2024
- RFC 5970DHCPv6 Options for Network BootCurrent
September 2010
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?