Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9666
Discuss this RFC: Send questions or comments to the mailing listlsr@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9666
Link-state routing protocols have hierarchical abstraction alreadybuilt into them. However, when lower levels are used for transit,they must expose their internal topologies to each other, therebyleading to scaling issues.
To avoid such issues, this document discusses extensions to the IS-ISrouting protocol that allow Level 1 (L1) areas to provide transit butonly inject an abstraction of the Level 1 topology into Level 2 (L2).Each Level 1 area is represented as a single Level 2 node, therebyenabling a greater scale.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.