Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework

Salam, S.; Senevirathne, T.; Aldrin, S.; Eastlake, D.

doi:10.17487/rfc7174

Search citation statements

Order By: Relevance

Paper Sections

Select...

Oam Packets1

Conventions Used In This Document1

Return Codes And1

Citation Types

Supporting

Mentioning

Contrasting

Year Published

2015

2016

Publication Types

Select...

Other2

Relationship

Self Cite2

Independent0

Authors

Journals

Cited by 2 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since RBridges cannot use OAM messages for the learning of MAC addresses (Section 3.2.1 of [RFC7174]), it will not lead to MAC address flip-flopping at a remote RBridge, even though RB1 uses its regular nicknames as ingress nicknames in its TRILL OAM messages, and at the same time RB1 uses RBvi's pseudo-nickname in its TRILL Data packets.…”

Section: Oam Packetsmentioning

confidence: 99%

Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active Access

Zhai¹,

Perlman²,

Senevirathne³

et al. 2016

Self Cite

View full text Add to dashboard Cite

Section: Oam Packetsmentioning

confidence: 99%

Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active Access

Zhai¹,

Perlman²,

Senevirathne³

et al. 2016

Self Cite

View full text Add to dashboard Cite

“…[RFC7174] presents the high-level format of OAM messages. The details of the TRILL OAM frame format are defined in this document.…”

Section: Conventions Used In This Documentmentioning

confidence: 99%

“…These parameters include MAID, Maintenance Domain Level (MD-Level), and MEP-IDs. The Base Mode for TRILL OAM defined here facilitates ease of use and provides out-of-the-box plug-and-play capabilities, supporting the operational and manageability considerations described in Section 6 of [RFC7174].…”

Section: Return Codes Andmentioning

confidence: 99%