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

Keep address and prefix associations distinct

02

IA_NA carries non-temporary address associations; IA_PD carries delegated-prefix associations.

Related RFCs and changes

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

DIAGRAM§ 12 ↗
RFC 9915 · § 12EXAMPLE
3 / 3
Keep address and prefix associations distinctIA_NA carries non-temporary address associations; IA_PD carries delegated-prefix associations.Client DUID + association contextIA_NA addressesIA_PD prefixesIA_TA retiredRFC 9915 removes the temporary-address assignment mechanism
03
Do not request the retired IA_TA mechanism.

Do not request the retired IA_TA mechanism.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 8415RFC 9915 § 1.1

RFC 9915 obsoletes IA_TA temporary-address assignment and the Server Unicast capability while applying verified errata.

Read the updated RFC section ↗
KEY POINT

DUID, IA type, and IAID identify the association context.

  • DUID, IA type, and IAID identify the association context.
  • Temporary-address assignment with IA_TA is obsoleted in this successor.
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 ↗