Visual RFC.
ALL RFCs / RFC 8415
Read the RFC ↗
RFC 8415 / PROTOCOL MECHANISMS

Select a server and request configuration

01

A typical DHCPv6 allocation uses Solicit, Advertise, Request, and Reply.

This guide explains the 2018 publication. Superseded by RFC 9915.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5 ↗
RFC 8415 · § 5EXAMPLE
3 / 3
Select a server and request configurationA typical DHCPv6 allocation uses Solicit, Advertise, Request, and Reply.clientserverSolicitAdvertiseRequestReplyconfigurationHistorical RFC 8415; RFC 9915 is its current successor
03
A Reply returns the selected configuration.

A Reply returns the selected configuration.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

DHCPv6 is a separate protocol from DHCPv4 and does not obtain the default router in the same way.

  • DHCPv6 is a separate protocol from DHCPv4 and does not obtain the default router in the same way.
  • Rapid Commit is a negotiated alternative, not an assumption that every exchange has four messages.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Select a server and request configuration
  2. Group bindings using DUID and IAID
  3. Delegate a prefix to a router
  4. Renew or rebind before validity ends
  5. Encapsulate an exchange through relays
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗