Dynamic adjustment of MLDP tunnel and PIM binding

Patent metadata

Field	Value
Publication number	US-9306758-B2
Application number	US-201313780234-A
Country	US
Kind code	B2
Filing date	Feb 28, 2013
Priority date	Feb 28, 2013
Publication date	Apr 5, 2016
Grant date	Apr 5, 2016

Abstract

A capability is provided for modifying association of a Multicast Label Distribution Protocol (MLDP) tunnel with Protocol Independent Multicast (PIM). Information associated with a multicast source and multicast group (multicast SG) is received. The multicast SG is associated with an MLDP tunnel. Association of the MLDP tunnel with an outgoing interface list of the multicast SG is modified by faking an Internet Group Management Protocol (IGMP) local membership operation for the multicast SG on the MLDP tunnel. Modifying association of the MLDP tunnel with the outgoing interface list of the multicast SG includes adding the MLDP tunnel to the outgoing interface list of the multicast SG by faking an IGMP local membership join for the multicast SG on the MLDP tunnel or removing the MLDP tunnel from the outgoing interface list of the multicast SG by faking an IGMP local membership prune for the multicast SG on the MLDP tunnel.

First claim

What is claimed is:

1. An apparatus, comprising:
a processor and a memory communicatively connected to the processor, the processor configured to:
receive information associated with a multicast source and multicast group (multicast SG) that is associated with a Multicast Label Distribution Protocol (MLDP) tunnel; and
modify association of the MLDP tunnel with an outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership operation for the multicast SG on the MLDP tunnel.

2. The apparatus of claim 1 , wherein the processor is configured to support an MLDP module supporting the MLDP and a Protocol Independent Multicast (PIM) module supporting a PIM protocol.

3. The apparatus of claim 2 , wherein the MLDP module is configured to:
detect creation or removal of the MLDP tunnel;
extract, from an MLDP Forwarding Equivalence Class (FEC), an encoded version of the information associated with the multicast SG; and
propagate, toward the PIM module, the encoded version of the information associated with the multicast SG.

4. The apparatus of claim 2 , wherein the PIM module is configured to:
receive, from the MLDP module, an encoded version of the information associated with the multicast SG;
decode the encoded version of the information associated with the multicast SG; and
identify the multicast SG based on the information associated with the multicast SG.

5. The apparatus of claim 1 , wherein the processor is configured to:
detect creation or removal of the MLDP tunnel;
extract, from an MLDP Forwarding Equivalence Class (FEC), an encoded version of the information associated with the multicast SG;
decode the encoded version of the information associated with the multicast SG; and
identify the multicast SG based on the information associated with the multicast SG.

6. The apparatus of claim 1 , wherein the processor is configured to modify association of the MLDP tunnel with the outgoing interface list of the multicast SG by:
adding the MLDP tunnel to the outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership join for the multicast SG on the MLDP tunnel.

7. The apparatus of claim 6 , wherein the processor is configured to support a Protocol Independent Multicast (PIM) module supporting a PIM protocol, wherein the processor is configured to fake the IGMP local membership join for the multicast SG on the MLDP tunnel by:
causing the PIM module to generate the IGMP local membership join such that the IGMP local membership join is directed to the PIM module.

8. The apparatus of claim 1 , wherein the processor is configured to modify association of the MLDP tunnel with the outgoing interface list of the multicast SG by:
removing the MLDP tunnel from the outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership prune for the multicast SG on the MLDP tunnel.

9. The apparatus of claim 8 , wherein the processor is configured to support a Protocol Independent Multicast (PIM) module supporting a PIM protocol, wherein the processor is configured to fake the IGMP local membership prune for the multicast SG on the MLDP tunnel by:
causing the PIM module to generate the IGMP local membership prune such that the IGMP local membership prune is directed to the PIM module.

10. The apparatus of claim 1 , wherein the processor is configured to:
designate a Protocol Independent Multicast (PIM) protocol as a designated router (DR) on the MLDP tunnel; and
propagate a PIM multicast group join message toward the multicast source, wherein the PIM multicast group join message comprises the information associated with the multicast SG.

11. A method, comprising:
using a processor and a memory for:
receiving information associated with a multicast source and multicast group (multicast SG) that is associated with a Multicast Label Distribution Protocol (MLDP) tunnel; and
modifying association of the MLDP tunnel with an outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership operation for the multicast SG on the MLDP tunnel.

12. The method of claim 11 , further comprising:
supporting an MLDP module supporting the MLDP and a Protocol Independent Multicast (PIM) module supporting a PIM protocol.

13. The method of claim 12 , further comprising using the MLDP module for:
creation or removal of the MLDP tunnel;
extracting, from an MLDP Forwarding Equivalence Class (FEC), an encoded version of the information associated with the multicast SG; and
propagating, toward the PIM module, the encoded version of the information associated with the multicast SG.

14. The method of claim 12 , further comprising using the PIM module for:
receiving, from the MLDP module, an encoded version of the information associated with the multicast SG;
decoding the encoded version of the information associated with the multicast SG; and
identifying the multicast SG based on the information associated with the multicast SG.

15. The method of claim 11 , further comprising:
detecting creation or removal of the MLDP tunnel;
extracting, from an MLDP Forwarding Equivalence Class (FEC), an encoded version of the information associated with the multicast SG;
decoding the encoded version of the information associated with the multicast SG; and
identifying the multicast SG based on the information associated with the multicast SG.

16. The method of claim 11 , wherein modifying association of the MLDP tunnel with the outgoing interface list of the multicast SG comprises:
adding the MLDP tunnel to the outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership join for the multicast SG on the MLDP tunnel.

17. The method of claim 16 , wherein the processor is configured to support a Protocol Independent Multicast (PIM) module supporting a PIM protocol, wherein faking the IGMP local membership join for the multicast SG on the MLDP tunnel comprises:
causing the PIM module to generate the IGMP local membership join such that the IGMP local membership join is directed to the PIM module.

18. The method of claim 11 , wherein modifying association of the MLDP tunnel with the outgoing interface list of the multicast SG comprises:
removing the MLDP tunnel from the outgoing interface list of the multicast SG by faking an Internet Group Management Protocol (IGMP) local membership prune for the multicast SG on the MLDP tunnel.

19. The method of claim 18 , wherein the processor is configured to support a Protocol Independent Multicast (PIM) module supporting a PIM protocol, wherein faking the IGMP local membership prune for the multicast SG on the MLDP tunnel comprises:
causing the PIM module to generate the IGMP local membership prune such that the IGMP local membership prune is directed to the PIM module.

20. The method of claim 11 , further comprising:
designating a Protocol Independent Multicast (PIM) protocol as a designated router (DR) on the MLDP tunnel; and
propagating a PIM multicast group join message toward the multicast source, wherein the PIM multicast group join message comprises the information associated with the multicast SG.

Assignees

• Kollipara Siva
• Kotalwar Jayant
• Alcatel Lucent

Inventors

• Kollipara Siva
• Kotalwar Jayant

Classifications

• H04L12/185 Primary

  with management of multicast group membership · CPC title

• H04L45/16 Primary

  Multipoint routing · CPC title

• H04L45/507

  Label distribution · CPC title

• H04L49/201

  Multicast operation; Broadcast operation · CPC title

• H04L61/2069

  Electricity · mapped topic