File formats:

Also available: XML file for editing

 

Status:

EXPERIMENTAL

Authors:

T. Li
S. Chen
V. Ilangovan
G. Mishra

Stream:

IETF

Source:

lsr (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9666

Discuss this RFC: Send questions or comments to the mailing list lsr@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9666

Abstract

Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues.

To avoid such issues, this document discusses extensions to the IS-IS routing protocol that allow Level 1 (L1) areas to provide transit but only inject an abstraction of the Level 1 topology into Level 2 (L2). Each Level 1 area is represented as a single Level 2 node, thereby enabling a greater scale.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.