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

Probe a neighbor that may be unreachable

03

Neighbor Unreachability Detection checks whether the forward path to a neighbor continues to work.

Related RFCs and changes

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

DIAGRAM§ 7.3 ↗
RFC 4861 · § 7.3EXAMPLE
3 / 3
Probe a neighbor that may be unreachableNeighbor Unreachability Detection checks whether the forward path to a neighbor continues to work.NEIGHBOR REACHABILITY STATESTALEDELAYPROBEconfirmation → REACHABLEA STALE mapping can still be used while checking reachability
03
A reachability confirmation returns the entry to REACHABLE.

A reachability confirmation returns the entry to REACHABLE.

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

REACHABLE, STALE, DELAY, and PROBE are distinct neighbor-cache states.

  • REACHABLE, STALE, DELAY, and PROBE are distinct neighbor-cache states.
  • A STALE entry can still be used while the reachability procedure progresses.
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 ↗