Multicast forwarding methods and apparatuses across autonomous systems
US-2024275714-A1 · Aug 15, 2024 · US
US9059943B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9059943-B2 |
| Application number | US-201314090164-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 26, 2013 |
| Priority date | Jun 9, 2006 |
| Publication date | Jun 16, 2015 |
| Grant date | Jun 16, 2015 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of routing multicast traffic in a computer network is disclosed. The method comprises associating a plurality of multicast group addresses on a network device with respective multicast routing topologies. A network device and a network are also disclosed.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving a multicast data packet at a network device; identifying a multicast group address of the multicast data packet; and in an automated operation based on the identified multicast group address and using one or more processors, performing a reverse path forwarding (RPF) check using a particular routing table corresponding to a particular multicast topology associated with the identified multicast group address, the network device having a plurality of routing tables corresponding to respective multicast group addresses. 2. The method of claim 1 , further comprising routing the multicast data packet in accordance with the particular routing table. 3. The method of claim 2 , further comprising determining that the RPF check for the multicast data packet has passed, the routing of the multicast data packet being responsive to passing of the RPF check. 4. The method of claim 1 , further comprising: determining that the RPF check for the multicast group address has failed; and responsive to failure of the RPF check, rejecting the multicast data packet. 5. The method of claim 1 , wherein the particular routing table used in performing the RPF check is a particular unicast routing table associated with the particular multicast topology, the network device having a plurality of unicast routing tables associated with respective multicast topologies. 6. The method of claim 1 , wherein the network device is configured to route packets in multiple autonomous routing domains. 7. The method of claim 6 , wherein the multiple autonomous routing domains include multicast virtual private networks. 8. The method of claim 7 , in which at least two of the virtual private networks have different multicast topologies. 9. The method of claim 1 , further comprising determining the particular routing table corresponding to the identified multicast group address by reading a statically configured multicast routing topology associated with the identified multicast group address. 10. A network device comprising: a network interface configured to receive a multicast data packet; an address reader module configured to identify a multicast group address of the multicast data packet; and a reverse path forwarding (RPF) module configured to perform, based on the identified multicast group address, a RPF check using a particular routing table corresponding to a particular multicast topology associated with the identified multicast group address, the network device having a plurality of routing tables corresponding to respective multicast group addresses. 11. The network device of claim 10 , further configured to route the multicast data packet in accordance with the particular routing table. 12. The network device of claim 11 , further configured such that the routing of the multicast data packet is performed in response to determining that the RPF check for the multicast data packet has passed. 13. The network device of claim 10 , further configured to reject the multicast data packet in response to determining that the RPF check for the multicast data packet has failed. 14. The network device of claim 10 , wherein the RPF module is configured such that the particular routing table used in performing the RPF check is a particular unicast routing table associated with the particular multicast topology, the network device having a plurality of unicast routing tables associated with respective multicast topologies. 15. The network device of claim 10 , wherein the network device is configured to route packets in multiple autonomous routing domains. 16. The network device of claim 15 , wherein the multiple autonomous routing domains include multicast virtual private networks. 17. The network device of claim 16 , in which at least two of the virtual private networks have different multicast topologies. 18. The network device of claim 10 , further comprising a determination module to determine the particular routing table corresponding to the identified multicast group address by reading a statically configured multicast routing topology associated with the identified multicast group address. 19. A non-transitory tangible computer readable storage media encoded with instructions that, when executed by a processor of a network device configured to perform networking resource resolution, cause the processor to: receive a multicast data packet at a network device; identify a multicast group address of the multicast data packet; and in an automated operation based on the identified multicast group address, perform a reverse path forwarding (RPF) check using a particular routing table corresponding to a particular multicast topology associated with the identified multicast group address, the network device having a plurality of routing tables corresponding to respective multicast group addresses. 20. The non-transitory computer readable storage media of claim 19 , further comprising instructions to cause the processor to: route the multicast data packet in accordance with the particular routing table. 21. The non-transitory computer readable storage media of claim 20 , further comprising instructions to cause the processor to: determine that the RPF check for the multicast data packet has passed, the routing of the multicast data packet being responsive to passing of the RPF check. 22. The non-transitory computer readable storage media of claim 19 , wherein the particular routing table used in performing the RPF check is a particular unicast routing table associated with the particular multicast topology, the network device having a plurality of unicast routing tables associated with respective multicast topologies. 23. The computer readable storage media of claim 19 , wherein the network device is configured to route packets in multiple autonomous routing domains. 24. The computer readable storage media of claim 19 , further comprising instructions to cause the processor to: determine the particular routing table corresponding to the identified multicast group address by reading a statically configured multicast routing topology associated with the identified multicast group address.
Address table lookup; Address filtering · CPC title
Dynamic adaptation of the update intervals, e.g. event-triggered updates · CPC title
Multipoint routing · CPC title
Organization of routing tables · CPC title
Backward learning · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.