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

Combine an advertised prefix and identifier

03

A suitable Prefix Information option with the Autonomous flag can drive global address formation.

Related RFCs and changes

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

RFC 4862 · § 5.5.3EXAMPLE
3 / 3
Combine an advertised prefix and identifierA suitable Prefix Information option with the Autonomous flag can drive global address formation.Router Advertisement: Prefix InformationA flag set?length?lifetimes?valid prefixinterface IDtentative address → required checksOn-link indication and autonomous configuration are different
03
Combine a valid prefix with the interface identifier and perform required address checks.

Combine a valid prefix with the interface identifier and perform required address checks.

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

Ignore it for SLAAC when the Autonomous flag is not set.

  • Ignore it for SLAAC when the Autonomous flag is not set.
  • The prefix length and interface-identifier length must fit the address length, and valid lifetime must not be less than preferred lifetime.
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. Form a tentative link-local address
  2. Check a tentative address for duplicates
  3. Combine an advertised prefix and identifier
  4. Track preferred and valid lifetimes
  5. Renumber without an instant cutover

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗