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

Validate a router redirect

04

A redirect can indicate a better first hop, but acceptance is constrained by the existing local routing context.

Related RFCs and changes

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

DIAGRAM§ 8.1 ↗
RFC 4861 · § 8.1EXAMPLE
3 / 3
Validate a router redirectA redirect can indicate a better first hop, but acceptance is constrained by the existing local routing context.hostcurrent routerbetter first hopcurrent pathRedirectother sendernot current routerRedirect authority is constrained by the existing first hop
03
Reject a redirect whose sender fails the required first-hop checks.

Reject a redirect whose sender fails the required first-hop checks.

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

The sender must be the current first-hop router for the destination.

  • The sender must be the current first-hop router for the destination.
  • Required checks include link-local source and Hop Limit 255; an arbitrary distant sender cannot be accepted as a redirect authority.
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

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 ↗