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

Choose a two-message or four-message exchange

01

DHCPv6 supports information-only exchanges and allocation exchanges with an explicitly negotiated Rapid Commit alternative.

Related RFCs and changes

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

DIAGRAM§ 5 ↗
RFC 9915 · § 5EXAMPLE
3 / 3
Choose a two-message or four-message exchangeDHCPv6 supports information-only exchanges and allocation exchanges with an explicitly negotiated Rapid Commit alternative.CHOOSE THE EXCHANGE FOR THE TASKsettings only?bindings?Information-requestReplynormal allocationSolicit → AdvertiseRequest → ReplyRapid Commit:Solicit → ReplyRapid Commit allocation is an explicit negotiated alternative
03
Use a two-message path only for the applicable information-only or negotiated Rapid Commit procedure.

Use a two-message path only for the applicable information-only or negotiated Rapid Commit procedure.

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

Information-request/Reply supplies configuration without an address allocation.

  • Information-request/Reply supplies configuration without an address allocation.
  • Normal allocation uses Solicit/Advertise/Request/Reply; Rapid Commit permits a specified Solicit/Reply allocation.
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. Choose a two-message or four-message exchange
  2. Keep address and prefix associations distinct
  3. Use binding lifetimes and contact timers correctly
  4. Carry link context in a relay envelope
  5. Separate configuration from trust and privacy
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗