RFC 8361: Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) Traffic
In plain English — editorial summary, not part of the RFC
In Transparent Interconnection of Lots of Links (TRILL) active-active access, a Reverse Path Forwarding (RPF) check failure issue may occur when using the pseudo-nickname mechanism specified in RFC 7781. This document describes a solution to resolve this RPF check failure issue through centralized replication. All ingress Routing Bridges (RBridges) send Broadcast, Unknown Unicast, and Multicast (BUM) traffic to a centralized node with unicast TRILL encapsulation. When the centralized node receives the BUM traffic, it decapsulates the packets and forwards them to their destination RBridges using a distribution tree established per the TRILL base protocol (RFC 6325). To avoid RPF check failure on an RBridge sitting between the ingress RBridge and the centralized replication node, some change in the RPF calculation algorithm is required. RPF checks on each RBridge MUST be calculated as if the centralized node was the ingress RBridge, instead of being calculated using the actual ingress RBridge. This document updates RFC 6325.
Document record
- Document ID
- RFC8361
- Published
- April 2018
- Authors
- W. Hao; Y. Li; M. Durrani; S. Gupta; A. Qu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 6325
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- 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 6327Routing Bridges (RBridges): AdjacencyObsoleted
July 2011
- RFC 6326Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISObsoleted
July 2011
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?