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

Compute a shortest-path tree

04

Each router computes routes from its link-state database using the shortest-path calculation.

Related RFCs and changes

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

RFC 2328 · § 16.1 — Shortest-path treeEXAMPLE
3 / 3
Compute a shortest-path treeEach router computes routes from its link-state database using the shortest-path calculation.SHORTEST-PATH TREE · EXAMPLE COSTS2215rootABtargetvia A: 2 + 2 = 4via B: 1 + 5 = 6Install next hop AThe calculating router is the tree root
03
Install the shortest-path next hop or equal-cost set.

Install the shortest-path next hop or equal-cost set.

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

The root is the calculating router; link costs determine the illustrative path choice.

  • The root is the calculating router; link costs determine the illustrative path choice.
  • Equal-cost multipath is possible; this is not an unconstrained policy protocol like BGP.
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 neighbors and form adjacencies
  2. Synchronize the link-state database
  3. Flood a newer link advertisement
  4. Compute a shortest-path tree
  5. Separate areas through the backbone
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗