RFC 7177: Transparent Interconnection of Lots of Links (TRILL): Adjacency
In plain English — editorial summary, not part of the RFC
The IETF Transparent Interconnection of Lots of Links (TRILL) protocol supports arbitrary link technologies between TRILL switches, including point-to-point links and multi-access Local Area Network (LAN) links that can have multiple TRILL switches and end stations attached. TRILL uses Intermediate System to Intermediate System (IS-IS) routing. This document specifies the establishment, reporting, and termination of IS-IS adjacencies between TRILL switches, also known as RBridges (Routing Bridges). It also concerns four other link-local aspects of TRILL: Designated RBridge (DRB) selection, MTU (Maximum Transmission Unit) testing, pseudonode creation, and BFD (Bidirectional Forwarding Detection) session bootstrapping in connection with adjacency. State diagrams are included where appropriate. This document obsoletes RFC 6327 and updates RFC 6325.
Document record
- Document ID
- RFC7177
- Published
- May 2014
- Authors
- D. Eastlake 3rd; R. Perlman; A. Ghanwani; H. Yang; V. Manral
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
Topics
Referenced by
5 later RFCs formally update or obsolete part of this document.
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 8139Transparent Interconnection of Lots of Links (TRILL): Appointed ForwardersCurrent
June 2017
- RFC 8249Transparent Interconnection of Lots of Links (TRILL): MTU NegotiationCurrent
September 2017
- RFC 8377Transparent Interconnection of Lots of Links (TRILL): Multi-TopologyCurrent
July 2018
- RFC 8564Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)Current
April 2019
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- RFC 7174Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
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 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 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- 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?