RFC 7177

Transparent Interconnection of Lots of Links (TRILL): Adjacency, May 2014

File formats:
icon for text file icon for PDF icon for HTML
RFC 6327
RFC 6325
Updated by:
RFC 7780, RFC 8139, RFC 8249, RFC 8377, RFC 8564
D. Eastlake 3rd
R. Perlman
A. Ghanwani
H. Yang
V. Manral
trill (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7177

Discuss this RFC: Send questions or comments to the mailing list trill@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7177


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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search