RFC 8377: Transparent Interconnection of Lots of Links (TRILL): Multi-Topology
In plain English — editorial summary, not part of the RFC
This document specifies extensions to the IETF TRILL (Transparent Interconnection of Lots of Links) protocol to support multi-topology routing of unicast and multi-destination traffic based on IS-IS (Intermediate System to Intermediate System) multi-topology specified in RFC 5120. This document updates RFCs 6325 and 7177.
Document record
- Document ID
- RFC8377
- Published
- July 2018
- Authors
- D. Eastlake 3rd; M. Zhang; A. Banerjee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8378Signal-Free Locator/ID Separation Protocol (LISP) MulticastCurrent
May 2018
- RFC 8379OSPF Graceful Link ShutdownCurrent
May 2018
- RFC 8380Directory-Assisted Transparent Interconnection of Lots of Links (TRILL) EncapsulationCurrent
May 2018
- RFC 8381Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel ProtocolCurrent
May 2018
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
- RFC 8383Transparent Interconnection of Lots of Links (TRILL): Address Flush MessageCurrent
May 2018
- RFC 8370Techniques to Improve the Scalability of RSVP-TE DeploymentsCurrent
May 2018
- RFC 8384Transparent Interconnection of Lots of Links (TRILL) Smart EndnodesCurrent
July 2018
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?