1. Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 Multicast in VPLS draft-raggarwa-l2vpn-vpls-mcast-01.txt draft-raggarwa-l2vpn-vpls-mcast-ctrl-00.txt Rahul Aggarwal (Juniper) Yuji Kamite (NTT) Luyuan Fang (AT&T)

2. 2 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Co-Authors  Yakov Rekhter (Juniper)  Chaitanya Kodeboniya (Juniper)

3. 3 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Agenda  Limitations of existing VPLS proposals for Multicast  VPLS Multicast Architecture  Where do the various drafts fit – Going forward  Conclusion

4. 4 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Current VPLS proposals:  “ Virtual Private LAN Service” ( draft-ietf-l2vpn-vpls- bgp )  “ Virtual Private LAN Services over MPLS ” ( draft-ietf- l2vpn-vpls-ldp )  Limitations of these proposals for VPLS multicast…

5. 5 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Limitations of current VPLS proposals for VPLS Multicast  Do not allow the use of P-Multicast Trees for VPLS multicast data traffic Desirable for optimizing bandwidth efficiency  PEs with VPLS sites that do not have receivers in a given multicast customer (S, G) receive traffic for that multicast stream  Focus on optimizing state and not bandwidth.

6. 6 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Design Objectives for multicast support in VPLS service (not a complete list)  A given customer (multicast) packet should traverse a given service provider link at most once  Deliver customer multicast traffic to only PEs that have (customer) receivers for that traffic  Deliver customer multicast traffic along the “optimal” paths within the service provider (from the ingress PE to the egress PEs) The amount of state within the service provider network required to support Multicast in VPLS service should be no greater than what is required to support unicast in VPLS service The overhead of maintaining the state to support Multicast in VPLS service should be no greater than what is required to support unicast in VPLS service Optimize Bandwidth: Optimize State: Optimizing Bandwidth and State are conflicting goals

7. 7 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net VPLS Multicast Architecture Control Plane  VPLS Auto-Discovery Use existing VPLS auto-discovery mechanisms  Allow elimination of flooding PE-CE IGMP/PIM snooping In VPLS a PE does not maintain a layer 3 adjacency with a CE PE-PE reliable exchange of multicast control messages Avoid PIM-IGMP snooping overhead on PWs BGP or LDP

8. 8 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net VPLS Multicast Architecture Data Plane Ingress Replication Separate Tree for Every C-(S, G) Separate Tree per-set-of VPLSs “Inclusive Mapping” Separate Tree per-set-of C-(S, G)s “Selective Mapping” Increasing P-router state and Bandwidth efficiency State = Unicast VPLS Unbounded State Aggregate State Tree = PIM, RSVP-TE P2MP LSPs, Receiver Initiated P2MP LSPs Decreasing P-router state and Bandwidth efficiency

9. 9 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Avoiding PIM Snooping on PWs Reliable Exchange of Multicast Control Messages between PEs (Eg. Using BGP) PE 1 CE-B2 CE-B3 PE 3 PE 2 PE 4 VPLS A Site 3 CE -A1 CE-B1 CE-A2 CE-A4 CE-A3 VPLS B Site 1 VPLS B Site 2 VPLS A Site 4 VPLS B Site 3 VSI-A VSI-B VRF-B VPLS A Site 2 VPLS A Site 1 VSI-A RR PEs have I-BGP Peering Only With the RR C-S -> C-G PIM Join C-S, C-G – Snooped at PE1 BGP VPLS Mcast Ctrl Information Update: <RD, C-S, C-G, Originator PE – PE1 Upstream PE – PE2, RT>

10. 10 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net VPLS Multicast Data Plane Tunnels  SP Multicast Trees Aggregate Trees (Inclusive Mapping) Aggregate Data Trees (Selective Mapping) Use PE-CE snooping and PE-PE Reliable multicast message exchange  Ingress Replication Existing VPLS proposals AND PE-CE snooping and PE-PE Reliable multicast message exchange

11. 11 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Functional Blocks for VPLS Multicast  Existing L2VPN WG VPLS proposals  Use of SP Multicast Trees for VPLS Multicast  IGMP Snooping on PE-CE links  PIM Snooping on PE-CE links  PE-PE reliable exchange of multicast control messages  Let us evaluate the various drafts and how to move forward with respect to this decomposition…

12. 12 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Where do the Various Drafts Fit in ?  Use of SP Multicast Trees for VPLS Multicast Draft-raggarwa-l2vpn-vpls-mcast-01.txt  IGMP snooping on PE-CE links draft-ietf-magma-snoop-12.txt  PIM snooping on PE-CE links Subset of draft-serbest-l2vpn-vpls-mcast-03.txt  Use of BGP for PE-PE reliable multicast control information propagation Draft-raggarwa-l2vpn-vpls-mcast-ctrl-00.txt  Use of LDP for PE-PE reliable multicast control information propagation Subset of draft-serbest-l2vpn-vpls-mcast-03.txt

13. 13 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Conclusion  Allign/Restructure the drafts to follow the functional decomposition  Move the drafts that do not require restructuring to WG drafts Draft-raggarwa-l2vpn-vpls-mcast-01.txt and draft-raggarwa-l2vpn-vpls-mcast-ctrl-00.txt  Move the other drafts to WG drafts after the requisite restructuring