Skip to main content

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

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Although TRILL is based on IS-IS, which supports multilevel unicast routing, extending TRILL to multiple levels …
Received changes through RFC Editor sync (changed abstract to '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 already-existing capabilities of IS-IS. One issue is with the handling of multi-destination packet distribution trees. Other issues are with TRILL switch nicknames. How are such nicknames allocated across a multilevel TRILL network? Do nicknames need to be unique across an entire multilevel TRILL network? Or can they merely be unique within each multilevel area?

This informational document enumerates and examines alternatives based on a number of factors including backward compatibility, simplicity, and scalability; it makes recommendations in some cases.')
2017-09-10
(System)
Received changes through RFC Editor sync (created alias RFC 8243, changed title to 'Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)', changed …
Received changes through RFC Editor sync (created alias RFC 8243, changed title to 'Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)', changed abstract to '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 already-existing capabilities of IS-IS. One issue is with the handling of multi-destination packet distribution trees. Other issues are with TRILL switch nicknames. How are such nicknames allocated across a multilevel TRILL network? Do nicknames need to be unique across an entire multilevel TRILL network? Or can they merely be unique within each multilevel area?', changed pages to 29, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-09-10, changed IESG state to RFC Published)
2017-09-10
(System) RFC published