Skip to main content

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames
RFC 8397

Revision differences

Document history

Date By Action
2018-05-31
(System)
Received changes through RFC Editor sync (created alias RFC 8397, changed title to 'Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames', …
Received changes through RFC Editor sync (created alias RFC 8397, changed title to 'Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames', changed abstract to '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.', changed pages to 16, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-31, changed IESG state to RFC Published)
2018-05-31
(System) RFC published