Transparent Interconnection of Lots of Links (TRILL): Adjacency

Perlman, Radia; Manral, Vishwas; Ghanwani, Anoop; Yang, Howard H.

doi:10.17487/rfc7177

Cited by 13 publications

(37 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This document provides other known clarifications, corrections, and updates to [RFC6325], [RFC7177], and [RFC7179]. This document obsoletes [RFC7180] (the previous TRILL "clarifications, corrections, and updates" document), updates [RFC6325], updates [RFC7177] as described in Section 9, and updates [RFC7179] as described in Sections 10.2 and 10.3. The changes to these RFCs are summarized in Appendix C.…”

Section: Rfc 7780mentioning

confidence: 99%

See 1 more Smart Citation

Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates

Manral¹,

Ghanwani²,

Banerjee³

et al. 2016

Self Cite

View full text Add to dashboard Cite

Since the publication of the TRILL (Transparent Interconnection of Lots of Links) base protocol in 2011, active development and deployment of TRILL have revealed errata in RFC 6325 and areas that could use clarifications or updates. RFC 7177, RFC 7357, and an intended replacement of RFC 6439 provide clarifications and updates with respect to adjacency, the TRILL ESADI (End Station Address Distribution Information) protocol, and Appointed Forwarders, respectively. This document provides other known clarifications, corrections, and updates. It obsoletes RFC 7180 (the previous "TRILL clarifications, corrections, and updates" RFC), and it updates RFCs 6325, 7177, and 7179.

show abstract

Section: Rfc 7780mentioning

confidence: 99%

“…In the event of any conflicts between this document and [RFC6325], [RFC7177], or [RFC7179], this document takes precedence.…”

Section: Precedence (Changed)mentioning

confidence: 99%

Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates

Manral¹,

Ghanwani²,

Banerjee³

et al. 2016

Self Cite

View full text Add to dashboard Cite

show abstract

“…For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL BFD Control frames to the other only if TRILL IS-IS has detected bidirectional connectivity; that is, the adjacency is in the 2-Way or Report state [RFC7177], and both RBridges indicate support of TRILL BFD is enabled. The BFD-Enabled TLV is used to indicate this as specified in [RFC6213].…”

Section: One-hop Trill Bfd Controlmentioning

confidence: 99%

“…-A TRILL BFD Control session has been established, -TRILL BFD Echo support is indicated by the RBridge that would potentially respond to the BFD Echo, -The adjacency is in the Report state [RFC7177], and -The TRILL BFD Echo originating RBridge wishes to make use of this optional feature.…”

Section: Trill Bfd Echo Protocolmentioning

confidence: 99%