IP Multicast with PIM-SM over a MPLS TE Core draft-raggarwa-pim-sm-mpls-te-00.txt Rahul Aggarwal Juniper Networks rahul@juniper.net www.juniper.net
Authors § Rahul Aggarwal (Juniper) § Tom Pusateri (Juniper) § Dino Farinacci (Procket) § Liming Wei (Redback) www.juniper.net
Agenda § Problem Statement § Motivation § Operation Overview § Conclusion www.juniper.net 3
Problem Statement § How do we provide an IP multicast service over a MPLS core that is multicast free ? • Edge routers support PIM-SM • MPLS core with Point to Multipoint Traffic Engineering LSP www.juniper.net
Motivation § How do we provide multicast service over a deployed MPLS core that is multicast free ? • Provider wants to keep BGP routes out of the core that are needed for RPF: hence unable to run PIM-SM in the core • Provider may want to keeping multicast routing state out of the core § Added benefit is Traffic Engineering for multicast traffic • QoS for content distribution • MPLS protection schemes can be used (fast reroute) § BGP is not needed for multicast RPF in the core • The core may be BGP free for unicast • Possible to have a truly BGP free core § Can increase deployment of IP multicast ! www.juniper.net
IP Multicast Over P2MP MPLS TE Multicast Video P2MP MPLS TE LSP PE1 Source R1 PE2 PE5 Multicast Video Receiver R2 PE3 PE4 R4 R3 www.juniper.net
Terminology § Spe: Source PE connected to the multicast traffic source § Rpe: PE connected to one or more receivers www.juniper.net
Operation Overview § PIM-SM control state exchange between PEs § MPLS P2MP LSP endpoint discovery i.e. Rpe discovery by the Spe § Mapping IP multicast traffic at the Spe to a P2MP LSP § RPF interface determination at the Rpe www.juniper.net 8
PIM-SM Between PEs § Edge routers need to exchange PIM-SM routing information • Have to support the PIM-SM extensions § For a (S, G) Rpe resolves S onto the Spe (BGP next-hop) advertising S § Rpe initiates a “remote” PIM-SM adjacency with Spe • Draft-raggarwa-pim-sm-remote-nbr-00.txt § Rpe sends Join/Prune messages to the Spe www.juniper.net 9
P2MP LSP Endpoint Discovery / Setup § Spe can treat a Rpe as a P2MP LSP leaf on receiving a (S, G) join • Dynamic discovery § Spe associates the (S, G) Join with a P2MP LSP • If needed Spe adds the Rpe as a new leaf to the P2MP LSP • Draft-raggarwa-mpls-p2mp-te-00.txt www.juniper.net 10
Mapping IP Multicast Traffic to a P2MP LSP § Spe creates a multicast forwarding entry for a (S, G) or (*, G) with the P2MP LSP as an OIF § P2MP LSP selection at the Spe • Local matter www.juniper.net 11
RPF Interface at the Rpe § Rpe uses a P2MP LSP as the RPF interface for a given (S, G) pair • Must be the same as the P2MP LSP used by the Spe for that (S, G) § Spe needs to communicate the (S, G) entry to P2MP LSP mapping to the Rpe § Join Ack Message • Propagates the Group Set associated with a P2MP LSP to the Rpe 12
Join Ack Message § Needed for RPF interface determination at the Receiver PE § Propagates the Group Sets – P2MP LSP association to the Receiver PE § Can have a list of route attributes § Associates the Group Sets in the message with the route attribute list § A route attribute is a TLV with an attribute value § A route attribute is defined for carrying the P2MP LSP identifier www.juniper.net
IP Multicast over P2MP MPLS TE Procedures: Example Multicast Video Source S1, Groups G1, G2 Spe1 (S1, G1), (S1, G1) (S1, G2) R1 Rpe3 Rpe1 MPLS Multicast Video R2 Receiver (S1, G1), (S1, G1), (S1, G2) Rpe2 P2MP - LSP 1 (S1, G2) (S1, G1) (S1, G2) P2MP - LSP 2 R3 (S1, G1) www.juniper.net
Conclusion § MPLS WG to work on the P2MP LSP setup • P2MP LSP setup is in the charter • Requirements and solutions being discussed § PIM-SM WG to do the PIM-SM extensions § Comments ? § WG taking on this work ? § http://www.ietf.org/internet-drafts/draft-raggarwa- pim-sm-mpls-te-00.txt www.juniper.net
Thank You
Recommend
More recommend
![Transporting Voice by Using IP The RTP Control Protocol [1/3] RTCP A companion control](https://c.sambuz.com/886603/transporting-voice-by-using-ip-the-rtp-control-protocol-1-s.jpg)