Skip to main content

Centralized Replication for BUM traffic in active-active edge connection

Document Type Replaced Internet-Draft (trill WG)
Expired & archived
Authors Hao Weiguo , Yizhou Li , Tao Han , Susan Hares , Muhammad Durrani , Sujay Gupta
Last updated 2015-10-14 (Latest revision 2014-08-29)
Replaced by draft-ietf-trill-centralized-replication, draft-ietf-trill-centralized-replication, draft-ietf-trill-centralized-replication
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd Susan Hares
IESG IESG state Replaced by draft-ietf-trill-centralized-replication
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


In TRILL active-active access scenario, RPF check failure issue may occur when pseudo-nickname mechanism in [TRILLPN] is used. This draft describes a solution to the RPF check failure issue through centralized replication for BUM (Broadcast, Unknown unicast, Mutlicast) traffic. The solution has all ingress RBs send BUM traffic to a centralized node via unicast TRILL encapsulation. When the centralized node receives the BUM traffic, it decapsulates the traffic and forwards the BUM traffic to all destination RBs using a distribution tree established via the TRILL base protocol. To avoid RPF check failure on a RBridge sitting between the ingress RBridge and the centralized replication node, some change of RPF calculation algorithm is required. RPF calculation on each RBridge should use the centralized node as ingress RB instead of the real ingress RBridge of RBv to perform the calculation.


Hao Weiguo
Yizhou Li
Tao Han
Susan Hares
Muhammad Durrani
Sujay Gupta

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)