CurrentPROPOSED STANDARDIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8397
Published
May 2018
Authors
M. Zhang; D. Eastlake 3rd; R. Perlman; H. Zhai; D. Liu
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
16
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8397-transparent-interconnection-of-lots-of-links-trill-multilevel-using-unique-nickn