RFC 8243: Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)

Although TRILL is based on IS-IS, which supports multilevel unicast routing, extending TRILL to multiple levels has challenges that are not addressed by the…

Read RFC 8243 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
Normative reference — RFC 7780: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Normative reference — RFC 7177: Transparent Interconnection of Lots of Links (TRILL): Adjacency
Normative reference — RFC 8139: Transparent Interconnection of Lots of Links (TRILL): Appointed Forwarders
Informative reference — RFC 7176: Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
Informative reference — RFC 7172: Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling
Informative reference — RFC 7357: Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol
Informative reference — RFC 6361: PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol
Informative reference — RFC 7781: Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active Access
Informative reference — RFC 3194: The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio
Informative reference — RFC 7783: Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL)

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9183: Single Nickname for an Area Border RBridge in Multilevel Transparent Interconnection of Lots of Links (TRILL)