Providing PIM-SM support for mRSVP-TE based multicast virtual private networks

1. A method for supporting protocol independent multicast sparse mode (PIM-SM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) in a source provider edge (PE) router, comprising the steps of: creating a protocol independent multicast (PIM) state, wherein the PIM state is an (S, G) state, wherein S represents one of a source and a source address and G represents one of a group and a sparse mode destination address; sending a first unicast data message to a rendezvous point (RP) PE router using the PIM state, wherein the first unicast data message is a PIM register message encapsulated as a unicast multiprotocol label switching (MPLS) packet; receiving a PIM join message from the RP PE router, wherein the PIM join message triggers creating a second PIM state, wherein the second PIM state is an (S, G) state; sending a second unicast data message to the RP PE router via a default multicast distribution tree (MDT) using the second PIM state, wherein the second unicast data message is different from the first unicast data message; receiving a PIM register-stop message from the RP PE router, wherein the PIM register-stop message suspends sending the second unicast data message; and sending multicast data traffic via the default MDT.

2. The method of claim 1 , wherein creating the PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF).

3. The method of claim 1 , wherein creating the second PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF) coupled to the default MDT.

4. The method of claim 1 , further comprising generating the data MDT comprising the steps of: monitoring a rate multicast data traffic within the default MDT; determining that the rate exceeds a threshold; sending a MDT join message to at least one receiver PE router in response to determining, wherein the MDT join message comprises an MDT number that identifies a data MDT; receiving a path message from the at least one receiver PE router and thereby forming the data MDT; and sending multicast data traffic via the data MDT.

5. The method of claim 4 , wherein the path message comprises a virtual private network identification (VPN ID) number, a customer source, and a customer group.

6. The method of claim 4 , wherein the path message comprises a virtual private network identification (VPN ID) number and a MDT number.

7. The method of claim 4 , wherein the MDT join message further comprises a customer source and a customer group.

8. The method of claim 4 , wherein sending multicast data traffic via the data MDT comprises switching multicast data traffic from the default MDT to the data MDT.

9. A method for supporting protocol independent multicast sparse-mode (PIM-SM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) in a rendezvous point (RP) provider edge (PE) router, comprising the steps of: receiving a protocol independent multicast (PIM) join message, wherein the PIM join message triggers creating a PIM state, wherein the PIM state is an (*, G) state; receiving a first unicast data message from a source PE router using the PIM state, wherein the first unicast data message is a PIM register message encapsulated as a unicast multiprotocol label switching (MPLS) packet; sending multicast data traffic to one or more receiver PE routers via a default multicast distribution tree (MDT) in response to receiving the first unicast data packet; sending a second PIM join message to the source PE router, wherein the second PIM join message triggers creating a second PIM state, wherein the second PIM state is an (S, G) state, wherein S represents one of a source and a source address and G represents one of a group and a sparse mode destination address; receiving a second unicast data message from a source PE router using the second PIM state, wherein the second unicast data message is different from the first unicast data message; and sending a PIM register-stop message to the source PE router in response to receiving the second unicast data message.

10. The method of claim 9 , further comprising decapsulating the first unicast data message to generate the PIM register message and sending the PIM register message to a rendezvous point customer edge (CE) router.

11. The method of claim 9 , wherein creating the PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF).

12. The method of claim 9 , wherein creating the second PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF).

13. A computer program product comprising computer executable instructions for supporting protocol independent multicast sparse-mode (PIM-SM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) stored on a non-transitory computer readable medium of a router that, when executed by a processor, cause the router to: create a protocol independent multicast (PIM) state, wherein the PIM state is an (S, G) state; send a first unicast data message to a rendezvous point (RP) PE router using the PIM state, wherein the first unicast data message is a PIM register message encapsulated as a unicast multiprotocol label switching (MPLS) packet; receive a PIM join message from the RP PE router, wherein the PIM join message triggers creating a second PIM state, wherein the second PIM state is an (S, G) state, wherein S represents one of a source and a source address and G represents one of a group and a sparse mode destination address; send a second unicast data message to the RP PE router via a default multicast distribution tree (MDT) using the second PIM state, wherein the second unicast data message is different from the first unicast data message; receive a PIM register-stop message from the RP PE router, wherein the PIM register-stop message suspends sending the second unicast data message; and send multicast data traffic via the default MDT.

14. The computer program product of claim 13 , wherein creating the PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF).

15. The computer program product of claim 13 , wherein creating the second PIM state comprises configuring a multidirectional inclusive provider multicast service interface (MI-PMSI) for an outgoing interface (OIF) coupled to the default MDT.

16. The computer program product of claim 13 , further comprising instructions for generating the data MDT comprising the steps of: monitoring a rate multicast data traffic within the default MDT; determining that the rate exceeds a threshold; sending a MDT join message to at least one receiver PE router in response to determining, wherein the MDT join message comprises an MDT number that identifies a data MDT; receiving a path message from the at least one receiver PE router and thereby forming the data MDT; and sending multicast data traffic via the data MDT.

17. The computer program product of claim 16 , wherein receiving the path message from at least one receiver PE router comprises triggering a third PIM state change.

18. The computer program product of claim 17 , wherein triggering the third PIM state change comprises configuring a selective provider multicast service interface (S-PMSI) for an outgoing interface (OIF).

19. The computer program product of claim 16 , wherein sending multicast data traffic via the data MDT comprises switching multicast data traffic from the default MDT to the data MDT.

20. The computer program product of claim 16 , wherein the path message comprises a virtual private network identification (VPN ID) number and a MDT number and the MDT join message comprises a customer source address, a customer group address, and a MDT number.