RFC 7176: Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
In plain English — editorial summary, not part of the RFC
The IETF Transparent Interconnection of Lots of Links (TRILL) protocol provides optimal pair-wise data frame forwarding without configuration in multi-hop networks with arbitrary topology and link technology; it also provides support for multipathing of both unicast and multicast traffic. This document specifies the data formats and code points for the IS-IS extensions to support TRILL. These data formats and code points may also be used by technologies other than TRILL. This document obsoletes RFC 6326.
Document record
- Document ID
- RFC7176
- Published
- May 2014
- Authors
- D. Eastlake 3rd; T. Senevirathne; A. Ghanwani; D. Dutt; A. Banerjee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 45
- Also known as
- —
- Obsoletes:
- RFC 6326
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7172Transparent Interconnection of Lots of Links (TRILL): Fine-Grained LabelingCurrent
May 2014
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
- RFC 7716Global Table Multicast with BGP Multicast VPN (BGP-MVPN) ProceduresCurrent
December 2015
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7783Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL)Current
February 2016
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?