Centralized Replication for BUM traffic in active-active edge connection
draft-ietf-trill-centralized-replication-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (trill WG)
Last updated 2015-11-02 (latest revision 2015-04-29)
Replaces draft-hao-trill-centralized-replication
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Donald Eastlake
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-trill-centralized-replication-02.txt

Abstract

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.

Authors

Hao Weiguo (haoweiguo@huawei.com)
Li Yizhou (liyizhou@huawei.com)
Muhammad Durrani (mdurrani@cisco.com)
Sujay Gupta (sujay.gupta@ipinfusion.com)
Andrew Qu (laodulaodu@gmail.com)
Tao Han (billow.han@huawei.com)

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