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

Discover routers and on-link prefixes

01

Router Solicitations can prompt Router Advertisements containing router and prefix information.

Related RFCs and changes

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

DIAGRAM§ 6.3 ↗
RFC 4861 · § 6.3EXAMPLE
3 / 3
Discover routers and on-link prefixesRouter Solicitations can prompt Router Advertisements containing router and prefix information.hostrouterRouter SolicitationRouter Advertisementrouter / prefix lifetimesdefault routerson-link prefixesRouter lifetime, on-link flag, and autonomous flag are distinct
03
Update default-router and on-link-prefix state separately.

Update default-router and on-link-prefix state separately.

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

A router’s lifetime and a prefix’s lifetime are separate.

  • A router’s lifetime and a prefix’s lifetime are separate.
  • A prefix’s on-link indication and autonomous-address-configuration indication have different meanings.
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. Discover routers and on-link prefixes
  2. Resolve a local neighbor address
  3. Probe a neighbor that may be unreachable
  4. Validate a router redirect
  5. Keep Neighbor Discovery on its trust boundary
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗