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

Form a tentative link-local address

01

An enabled interface combines the link-local prefix with an interface identifier.

Related RFCs and changes

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

DIAGRAM§ 5.3 ↗
RFC 4862 · § 5.3EXAMPLE
3 / 3
Form a tentative link-local addressAn enabled interface combines the link-local prefix with an interface identifier.interface enabledlink-local prefixinterface identifiercombinetentative link-local addressTentative does not mean unique; identifier generation is separate
03
Mark the resulting address tentative before duplicate detection.

Mark the resulting address tentative before duplicate detection.

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

Creating a tentative address does not yet prove it is unique.

  • Creating a tentative address does not yet prove it is unique.
  • Interface identifier length and generation depend on other relevant specifications; do not assume all addresses expose a MAC address.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗