Optimized protocol independent multicast assert mechanism

Patent metadata

Field	Value
Publication number	US-2018367451-A1
Application number	US-201715625855-A
Country	US
Kind code	A1
Filing date	Jun 16, 2017
Priority date	Jun 16, 2017
Publication date	Dec 20, 2018
Grant date	—

Abstract

In a network environment using a PIM (Protocol Independent Multicast) multicast routing protocol, an Assert mechanism is implemented wherein a provider-edge (PE) device sends an Assert message on the Default MDT (multicast distribution tree) and causes selection of an Assert winner, wherein any ingress PE not selected as the Assert winner stops forwarding the data packets on the Data MDT; and the Assert winner sends periodic PIM control messages on the Default MDT to maintain the Assert state on all ingress PE routers until canceled or timed out. The Assert message is created in response to MDT Mapping from at least one other ingress PE device. The PIM control messages may contain a special bit extension which forces an RPF (reverse path forwarding) neighbor to keep pointing to the Assert winner until a PIM neighborship-down event is detected. This obviates the need for periodic Assert messaging and/or data packet punting.

First claim

What is claimed is:

1 . A method for triggering an Assert mechanism with multicast traffic in multi-homed networks running a PIM (Protocol Independent Multicast) multicast routing protocol, comprising:
an ingress provider edge (PE) device, which forwards data packets for a particular (S,G) (source-group pair) data flow on a Data MDT (multicast distribution tree), receiving on a Default MDT Data MDT Mapping from at least one other ingress PE device; the ingress PE device sending an Assert message on the Default MDT and causing selection of an Assert winner, wherein any ingress PE not selected as the Assert winner stops forwarding the data packets on the Data MDT; and the Assert winner sending periodic PIM control messages on the Default MDT to maintain the Assert state on all ingress PE routers.

2 . The method of claim 1 , wherein the Assert mechanism is triggered without a need to decapsulate the data packets.

3 . The method of claim 1 , wherein the Assert mechanism is triggered when the ingress PE device detects a PIM Join targeted towards another ingress PE device on a same multi-access segment.

4 . The method of claim 1 , wherein some ingress PE's send data packets over a Data MDT that is different from a Data MDT of other ingress PE's.

5 . The method of claim 1 , wherein the Assert message comprises a special bit extension, wherein the special bit extension forces an RPF neighbor to keep pointing to the Assert winner until a PIM neighborship-down event is detected.

6 . The method of claim 5 , wherein the PIM neighborship-down event comprises an event selected from an Assert cancel message, expiration of the Assert winner state, and Bidirectional Forwarding Detection (BFD).

7 . The method of claim 5 , further comprising sending a Hello message with a special option field value to all connected PE devices to ensure that a PE device receiving the Assert message following the Hello message is configured to interpret the Assert message having the special bit extension.

8 . An apparatus, comprising:
one or more network interfaces that communicate multicast traffic in multi-homed networks comprising a Data MDT (multicast distribution tree) and a Default MDT; a processor coupled to the one or more network interfaces and configured to execute a process; and a memory configured to store program instructions which contain the process executable by the processor, the process comprising: receiving on Default MDT at an ingress provider edge (PE) device, which forwards data packets for a particular (S,G) (source-group pair)data flow on the Data MDT, Data MDT Mapping from at least one other ingress PE device; sending from the ingress PE device a PIM Assert message on the Default MDT and causing selection of an Assert winner, wherein any ingress PE not selected as the Assert winner stops forwarding the data packets on the Data MDT; and sending from the Assert winner periodic PIM control messages on the Default MDT to maintain the Assert state on all ingress PE routers.

9 . The apparatus of claim 8 , wherein the Assert winner is determined without a need to decapsulate the data packets at a PE device.

10 . The apparatus of claim 8 , wherein Assert mechanism is triggered when the ingress PE device detects a PIM Join targeted towards another ingress PE device on a same multi-access segment.

11 . The apparatus of claim 8 , wherein some ingress PE's send data packets over a Data MDT that is different from a Data MDT of other PE's.

12 . The apparatus of claim 8 , wherein the Assert message comprises a special bit extension, wherein the special bit extension forces an RPF neighbor to keep pointing to the Assert winner until a PIM neighborship-down event is detected.

13 . The apparatus of claim 12 , wherein the PIM neighborship-down event comprises an event selected from an Assert cancel message, expiration of the Assert winner state, and Bidirectional Forwarding Detection (BFD).

14 . The apparatus of claim 12 , wherein the process further comprises sending a Hello message with a special option field value to all connected PE devices to ensure that a PE device receiving the Assert message following the Hello message is configured to interpret the Assert message having the special bit extension.

15 . A tangible non-transitory computer readable medium storing program instructions that cause a computer to execute a process, the process comprising:
receiving on a Default MDT (multicast distribution tree) at an ingress provider edge (PE) device, which forwards data packets for a particular (S,G) (source-group pair) data flow on a Data MDT, Data MDT Mapping from at least one other ingress PE device; sending from the ingress PE device a PIM Assert message on the Default MDT and causing selection of an Assert winner, wherein any ingress PE not selected as the Assert winner stops forwarding the data packets on the Data MDT; and sending from the Assert winner periodic PIM control messages on the Default MDT to maintain the Assert state on all ingress PE routers.

16 . The tangible non-transitory computer readable medium of claim 15 , wherein the Assert winner is determined without a need to decapsulate the data packets at a PE device.

17 . The tangible non-transitory computer readable medium of claim 15 , wherein the Assert mechanism is triggered when the ingress PE device detects a PIM Join targeted towards another ingress PE device on a same multi-access segment.

18 . The tangible non-transitory computer readable medium of claim 15 , wherein the Assert message comprises a special bit extension, wherein the special bit extension forces an RPF neighbor to keep pointing to the Assert winner until a PIM neighborship-down event is detected.

19 . The tangible non-transitory computer readable medium of claim 15 , the process further comprising sending a Hello message with a special option field value to all connected PE devices to ensure that a PE device receiving the Assert message following the Hello message is configured to interpret the Assert message having the special bit extension.

20 . The tangible non-transitory computer readable medium of claim 18 , wherein the PIM neighborship-down event comprises an event selected from an Assert cancel message, expiration of the Assert winner state, and Bidirectional Forwarding Detection (BFD).

Assignees

• Cisco Tech Inc

Inventors

• Gulrajani Sameer R
• Subramanian Karthik
• Agrawal Swadesh

Classifications

• H04L45/16

  Multipoint routing · CPC title

• H04L45/026

  Details of "hello" or keep-alive messages · CPC title

• H04L45/54 Primary

  Organization of routing tables · CPC title

• H04L12/1886

  with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains · CPC title