File formats:

Status:

PROPOSED STANDARD

Authors:

M. Zhang
D. Eastlake 3rd
R. Perlman
H. Zhai
D. Liu

Stream:

IETF

Source:

trill (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

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

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

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

Abstract

TRILL (Transparent Interconnection of Lots of Links) routing can be extended to support multiple levels by building on the multilevel feature of IS-IS routing. Depending on how nicknames are managed, there are two primary alternatives to realize TRILL multilevel: the unique nickname approach and the aggregated nickname approach as discussed in RFC 8243. This document specifies a unique nickname approach. This approach gives unique nicknames to all TRILL switches across the multilevel TRILL campus.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.