RFC 7180: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7780.
Current version: RFC 7780 — Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
In plain English — editorial summary, not part of the RFC
The IETF Transparent Interconnection of Lots of Links (TRILL) protocol provides least-cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topology and link technology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using Intermediate System to Intermediate System (IS-IS) link-state routing and by encapsulating traffic using a header that includes a hop count. Since publication of the TRILL base protocol in July 2011, active development of TRILL has revealed errata in RFC 6325 and some cases that could use clarifications or updates. RFCs 6327 and 6439 provide clarifications and updates with respect to adjacency and Appointed Forwarders. This document provides other known clarifications, corrections, and updates to RFCs 6325, 6327, and 6439.
Document record
- Document ID
- RFC7180
- Published
- May 2014
- Authors
- D. Eastlake 3rd; M. Zhang; A. Ghanwani; V. Manral; A. Banerjee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
- Obsoleted by:
- RFC 7780
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 6326Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISObsoleted
July 2011
- RFC 7177Transparent Interconnection of Lots of Links (TRILL): AdjacencyUpdated
May 2014
- RFC 7173Transparent Interconnection of Lots of Links (TRILL) Transport Using PseudowiresCurrent
May 2014
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- RFC 7179Transparent Interconnection of Lots of Links (TRILL): Header ExtensionUpdated
May 2014
- RFC 7178Transparent Interconnection of Lots of Links (TRILL): RBridge Channel SupportUpdated
May 2014
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?