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

Group bindings using DUID and IAID

02

A DHCP Unique Identifier identifies a participant; an Identity Association groups related leases under an IAID.

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§ 11 ↗
RFC 8415 · § 11EXAMPLE
3 / 3
Group bindings using DUID and IAIDA DHCP Unique Identifier identifies a participant; an Identity Association groups related leases under an IAID.DUID: client identityIA_NA · IAID 1IA_PD · IAID 2address bindingsprefix bindingsDUID need not be a MAC address; IA type is part of the context
03
Associate address or prefix bindings with that IA.

Associate address or prefix bindings with that IA.

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

A DUID need not equal a hardware MAC address.

  • A DUID need not equal a hardware MAC address.
  • IA_NA and IA_PD have different purposes; the IAID is interpreted with the client identity and IA type.
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 ↗