Alternatives for Multilevel Transparent Interconnection of Lots of Links
RFC 8243, “Alternatives for Multilevel Transparent Interconnection of Lots of Links”, is an Informational document published in September 2017 by R. Perlman, D. Eastlake 3rd, M. Zhang, A. Ghanwani, H. Zhai. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8243 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8242 Interface to the Routing System Ephemeral State Requirements
- RFC 8244 Special-Use Domain Names Problem Statement
- RFC 8241 Interface to the Routing System Security-Related Requirements
- RFC 8245 Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
- RFC 8240 Report from the Internet of Things Software Update Workshop 2016
- RFC 8246 HTTP Immutable Responses
- RFC 8239 Data Center Benchmarking Methodology
- RFC 8247 Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2