Bidirectional multicast protocol with upstream and downstream join messages

• US 7,808,993 B2
• Filed: 10/26/2005
• Issued: 10/05/2010
• Est. Priority Date: 10/26/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Farinacci, Dino, Zwiebel, John M.
• Primary Examiner(s): Shah; Chirag G
• Assistant Examiner(s): MITCHELL, DANIEL D
• Application Number:
  US11/258,641
• Publication Number:
  US 20070091891A1
• Time in Patent Office: 1,805 Days
• Field of Search: 370/230, 370/254, 370/256, 370/351, 370/389, 370/390, 370/395.3, 370/395.31, 370/395.2, 370/432, 370/392
• US Class Current: 370/392
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 45/16 Multipoint routing

Abstract

Systems and methods for implementing a bidirectional multicast protocol with two types of join messages are disclosed. The two types of join messages, upstream joins and downstream joins, are used to control the Reverse Path Forwarding (RPF) interface is added to the outgoing interface list for a particular multicast group, which in turn controls when multicast packets will be forwarded to the rendezvous point. One method involves receiving a multicast packet addressed to multicast group G. The method inhibits the multicast packet from being forwarded via the RPF interface, unless the outgoing interface list corresponding to the multicast group G already identifies the RPF interface. The RPF interface can be added to the outgoing interface list in response to reception of a downstream join message via the RPF interface, as well as in response to monitoring, via the RPF interface, an upstream join message on a shared network segment.

Claims

1. A method comprising:

receiving a multicast packet addressed to multicast group G, wherein

multicast routing for multicast group G is performed using a bidirectional multicast routing protocol,

the multicast packet is received via an interface, and

the interface is not a Reverse Path Forwarding (RPF) interface leading towards a rendezvous point;

inhibiting the multicast packet from being forwarded via the RPF interface,

wherein information associated with multicast group G indicates that the RPF interface is not an outgoing interface for multicast group G, and

the inhibiting is performed in response to the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G; and

generating (*, G) state information for the multicast group G, in response to receiving an indication that a receiver is joining the multicast group, wherein

the indication is received via the interface, and

the (*, G) state information includes, subsequent to the generating, the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G.

2. The method of claim 1, further comprising:

receiving a downstream join message identifying the multicast group G, wherein the downstream join message is received via the RPF interface; and

associating information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to receiving the downstream join message.

3. The method of claim 1, further comprising:

detecting an upstream join message specifying the multicast group G, wherein the upstream join message is detected by monitoring a shared network segment; and

associating information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to detecting the upstream join message.

4. The method of claim 1, further comprising:

sending a downstream join message identifying the multicast group G to one or more downstream network devices, wherein

the sending comprises sending the downstream join message via a non-reverse path forwarding interface.

5. The method of claim 4, wherein

the sending the downstream join message is performed in response to at least one of:

more than one outgoing interface being identified as an outgoing interface for multicast group G;

the RPF interface being identified as an outgoing interface for multicast group G; and

only one of a plurality of downstream interfaces being identified as an outgoing interface for multicast group G, wherein if only one of the downstream interfaces is identified as an outgoing interface for multicast group G, the sending the downstream join message comprises sending the downstream join message from each downstream interface other than the one of the downstream interfaces identified as an outgoing interface for multicast group G.

6. The method of claim 5, wherein

the sending the downstream join message comprises sending the downstream join message from each one of a plurality of interfaces.

7. A node comprising:

an interface, wherein

the interface is configured to receive a multicast packet addressed to multicast group G;

a Reverse Path Forwarding (RPF) interface coupled to send packets towards a rendezvous point; and

a bidirectional multicast routing module coupled to the interface and the RPF interface, wherein

information associated with multicast group G indicates that the RPF interface is not an outgoing interface for multicast group G,

the bidirectional multicast routing module is configured to inhibit the multicast packet from being forwarded via the RPF interface in response to the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G, and

the bidirectional multicast routing module is further configured to generate (*, G) state information for a multicast group G, in response to reception of an indication that a receiver is joining the multicast group, wherein the indication is received via the interface, and

the (*, G) state information includes, subsequent to generation of the (*, G) state, the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G.

8. The node of claim 7, wherein the bidirectional multicast routing module is further configured to:

associate information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to reception of a downstream join message identifying the multicast group G, wherein the downstream join message is received via the RPF interface.

9. The node of claim 7, wherein

the bidirectional multicast routing module is further configured to detect an upstream join message specifying the multicast group G,

the upstream join message is detected by monitoring a shared network segment, and

the bidirectional multicast routing module is configured to associate information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to detection of the upstream join message.

10. The node of claim 7, wherein

the bidirectional multicast routing module is configured to send a downstream join message identifying the multicast group G to one or more downstream network devices, wherein

the sending comprises sending the downstream join message via a non-reverse path forwarding interface.

11. The node of claim 10, wherein

the downstream join message is sent in response to at least one of:

more than one outgoing interface being identified as an outgoing interface for multicast group G;

the RPF interface being identified as an outgoing interface for multicast group G; and

only one of a plurality of downstream interfaces being identified as an outgoing interface for multicast group G, wherein if only one of the downstream interfaces is identified as an outgoing interface for multicast group G, the downstream join message is sent from each downstream interface other than the one of the downstream interfaces identified as an outgoing interface for multicast group G.

12. A system comprising:

means for receiving a multicast packet addressed to multicast group G, wherein

multicast routing for multicast group G is performed using a bidirectional multicast routing protocol,

the multicast packet is received via an interface, and

the interface is not a Reverse Path Forwarding (RPF) interface leading towards a rendezvous point;

means for inhibiting the multicast packet from being forwarded via the RPF interface, wherein

information associated with multicast group G indicates that the RPF interface is not an outgoing interface for multicast group G, and

the inhibiting is performed in response to the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G; and

means for generating (*, G) state information for the multicast group G, in response to receiving an indication that a receiver is joining the multicast group, wherein

the indication is received via the interface, and

the (*, G) state information includes, subsequent to the generating, the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G.

13. The system of claim 12, further comprising:

means for receiving a downstream join message identifying the multicast group G, wherein

the downstream join message is received via the RPF interface; and

means for associating information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to receiving the downstream join message.

14. The system of claim 12, further comprising:

means for detecting an upstream join message specifying the multicast group G, wherein

the upstream join message is detected by monitoring a shared network segment; and

means for associating information with multicast group G indicating that the RPF interface is an outgoing interface for multicast group G, in response to detecting the upstream join message.

15. The system of claim 12, further comprising:

means for sending a downstream join message identifying the multicast group G to one or more downstream network devices, wherein

the sending comprises sending the downstream join message via a non-reverse path forwarding interface.

16. The system of claim 15, wherein

the downstream join message is sent in response to at least one of:

more than one outgoing interface being identified as an outgoing interface for multicast group G;

the RPF interface being identified as an outgoing interface for multicast group G; and

only one of a plurality of downstream interfaces being identified as an outgoing interface for multicast group G, wherein if only one of the downstream interfaces is identified as an outgoing interface for multicast group G, the downstream join message is sent from each downstream interface other than the one of the downstream interfaces identified as an outgoing interface for multicast group G.

17. A method comprising:

receiving a multicast packet addressed to multicast group G, wherein

multicast routing for multicast group G is performed using a bidirectional multicast routing protocol,

the multicast packet is received via an interface, and the interface is not a Reverse Path Forwarding (RPF) interface leading towards a rendezvous point; and

inhibiting the multicast packet from being forwarded via the RPF interface, wherein information associated with multicast group G indicates that the RPF interface is not an outgoing interface for multicast group G, and

the inhibiting is performed in response to the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G.

18. A node comprising:

an interface, wherein

the interface is configured to receive a multicast packet addressed to multicast group G;

a Reverse Path Forwarding (RPF) interface coupled to send packets towards a rendezvous point; and

a bidirectional multicast routing module coupled to the interface and the RPF interface, wherein

information associated with multicast group G indicates that the RPF interface is not an outgoing interface for multicast group G, and

the bidirectional multicast routing module is configured to inhibit the multicast packet from being forwarded via the RPF interface in response to the information associated with multicast group G indicating that the RPF interface is not an outgoing interface for multicast group G.