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

Keep Neighbor Discovery on its trust boundary

05

Link-local checks limit some remote injection but do not authenticate every local sender.

Related RFCs and changes

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

DIAGRAM§ 11 ↗
RFC 4861 · § 11EXAMPLE
3 / 3
Keep Neighbor Discovery on its trust boundaryLink-local checks limit some remote injection but do not authenticate every local sender.Candidate Neighbor Discovery messageHop Limit checkwrong valuedrop255 passes only this checkon-link forgery still possibleLink-local validation is not cryptographic router authentication
03
A valid Hop Limit alone still does not prove a trusted router identity.

A valid Hop Limit alone still does not prove a trusted router identity.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 2461RFC 4861 Appendix F

The revision removes assumptions about IPsec AH/ESP in message validation and adds a separate securing-ND discussion.

Read the updated RFC section ↗
KEY POINT

ND messages have message-specific validation, including Hop Limit 255.

  • ND messages have message-specific validation, including Hop Limit 255.
  • An on-link attacker can still forge valid-looking control traffic without additional protection.
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 ↗