1. Centralized Replication for BUM traffic in active-active edge connection draft-hao-trill-centralized-replication-02 Weiguo Hao Huawei Yizhou Li Huawei Tao Han Huawei Muhammad Durrani Brocade Sujay Gupta IP Infusion Andrew Qu MediaTec Nov, 2014 Honolulu

2. Motivation Nov, 2014IETF 91 Honolulu2 Trill Campus RB 1 RB 2 RB 3 CE1 MC-LAG1 RB n Different flows with the same src MAC1 To avoid MAC flip-flop on remote RBn, same pseudo-nickname is used as ingress nickname on RB1,RB2 and RB3. Learning from data: no MAC flip-flop ; RPF check failure issue Centralized replication solution can be used to solve RPF check failure issue. Combined with pseudo-nickname, it can provide comprehensive TRILL active-active solution.

3. Solution Overview 3 Nov, 2014 IETF 91 Honolulu RB1RB2RB3 CE1 RB4 CE2 LAG1 Root RB6 RB7 1,BUM packet 2,Ingress RB sends BUM packet to Root node using unicast TRILL encapsulation. RB5 CE3 3.Root node decapsulates unicast TRILL encapsulation, replicates and forwards the BUM traffic to all destination RBs along TRILL distribution tree. 7,Original BUM packet 4.Multicast TRILL encapsulation. 5.Does RPF check as if the ingress was the tree Root. 6. Ingress nickname is used for traffic filtering to avoid loop. Assuming CE1,CE2 and CE3 are in same VLAN.

4. Local forwarding behavior on ingress RBridge(1) 4Nov, 2014IETF 91 Honolulu Centralized local forwarding behavior A (Ingress RB isn’t centralized node) : 1. Local replication to the ports associated with the same pseudo-nickname as that associated to the incoming port as per RFC6325. 2. Do not replicate to mc-lag port associated with different pseudo-nickname. 3. Do not replicate to non mc-lag ports.

5. Local forwarding behavior on ingress RBridge(2) 5Nov, 2014IETF 91 Honolulu Centralized local forwarding behavior B (Ingress RB is centralized node) : 1. Local replication to the ports associated with the same pseudo-nickname as that associated to the incoming port as per RFC6325. 2. Local replication to the mc-lag DF port associated with different pseudo-nickname as per RFC6325. Do not replicate to mc-lag non-DF port associated with different pseudo-nickname. 3. Local replication to non mc-lag ports.

6. BUM traffic load balancing among multiple centralized nodes Nov, 2014IETF 91 Honolulu6 1.VLAN-based load balancing 2.Flow-based load balancing  Same anycast special use nickname attached to all centralized nodes.  Anycast nickname used as egress nickname for the unicast TRILL encapsulation BUM traffic from ingress RB. The traffic will arrive at any one of the centralized nodes.

7. TRILL extension Nov, 2014IETF 91 Honolulu7 NICKFLAG RECORD C: Indicate the Nickname is exclusively used for centralized replication solution purpose. Ingress RBs use the nickname as egress nickname in TRILL header of unicast TRILL encapsulation for BUM traffic. +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Nickname | +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |IN| C| RESV | +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

8. Next Step Seek some comments and feedbacks WG adoption? Nov, 20148IETF 91 Honolulu