Network device with service and client routing elements configured to support any-source multicast extranets
First Claim
1. An apparatus comprising:
- a first network device adapted for communication with a plurality of other network devices;
the first network device comprising;
a service routing element configured with a first anycast rendezvous point address so as be an anycast rendezvous point peer with at least a second network device in a service routing domain; and
a client routing element configured with a second anycast rendezvous point address so as to be an anycast rendezvous point peer with at least a third network device in a client routing domain;
wherein the first network device is configured to receive in its service routing element from a service routing element of the second network device a register message identifying a multicast source, and to provide at least a portion of the register message from its service routing element to its client routing element in a manner that allows the third network device to learn the identity of the multicast source from the client routing element;
wherein the first network device comprises a provider edge device spanning the service and client routing domains; and
wherein the third network device comprises a customer edge device in the client routing domain.
5 Assignments
0 Petitions
Accused Products
Abstract
A first network device comprises a service routing element and a client routing element. The service routing element is configured with a first anycast rendezvous point address so as be an anycast rendezvous point peer with at least a second network device in a service routing domain. The client routing element is configured with a second anycast rendezvous point address so as to be an anycast rendezvous point peer with at least a third network device in a client routing domain. The first network device receives in its service routing element from a service routing element of the second network device a register message identifying a multicast source, and provides at least a portion of the register message from its service routing element to its client routing element in a manner that allows the third network device to learn the identity of the multicast source from the client routing element.
-
Citations
20 Claims
-
1. An apparatus comprising:
-
a first network device adapted for communication with a plurality of other network devices; the first network device comprising; a service routing element configured with a first anycast rendezvous point address so as be an anycast rendezvous point peer with at least a second network device in a service routing domain; and a client routing element configured with a second anycast rendezvous point address so as to be an anycast rendezvous point peer with at least a third network device in a client routing domain; wherein the first network device is configured to receive in its service routing element from a service routing element of the second network device a register message identifying a multicast source, and to provide at least a portion of the register message from its service routing element to its client routing element in a manner that allows the third network device to learn the identity of the multicast source from the client routing element; wherein the first network device comprises a provider edge device spanning the service and client routing domains; and wherein the third network device comprises a customer edge device in the client routing domain. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. An apparatus comprising:
-
a first network device adapted for communication with a plurality of other network devices; the first network device comprising; a service routing element configured with a first anycast rendezvous point address so as be an anycast rendezvous point peer with at least a second network device in a service routing domain; and a client routing element configured with a second anycast rendezvous point address so as to be an anycast rendezvous point peer with at least a third network device in a client routing domain; wherein the first network device is configured to receive in its service routing element from a service routing element of the second network device a register message identifying a multicast source, and to provide at least a portion of the register message from its service routing element to its client routing element in a manner that allows the third network device to learn the identity of the multicast source from the client routing element; and wherein the client routing element replicates the register message to at least one of its anycast rendezvous point peers for delivery over a (*,G) multicast tree that was previously created in response to a (*,G) join message not designating any particular multicast source, where G denotes a multicast group. - View Dependent Claims (13)
-
-
14. A method comprising:
-
configuring a service routing element of a first network device with a first anycast rendezvous point address such that the service routing element of the first network device is an anycast rendezvous point peer with at least a second network device in a service routing domain; configuring a client routing element of the first network device with a second anycast rendezvous point address such that the client routing element of the first network device is an anycast rendezvous point peer with at least a third network device in a client routing domain; receiving in the service routing element of the first network device from a service routing element of the second network device a register message identifying a multicast source; and providing at least a portion of the register message from the service routing element of the first network device to the client routing element of the first network device in a manner that allows the third network device to learn the identity of the multicast source from the client routing element; wherein the first network device comprises a provider edge device spanning the service and client routing domains; and wherein the third network device comprises a customer edge device in the client routing domain. - View Dependent Claims (15, 16, 17)
-
-
18. A method comprising:
-
configuring a service routing element of a first network device with a first anycast rendezvous point address such that the service routing element of the first network device is an anycast rendezvous point peer with at least a second network device in a service routing domain; configuring a client routing element of the first network device with a second anycast rendezvous point address such that the client routing element of the first network device is an anycast rendezvous point peer with at least a third network device in a client routing domain; receiving in the service routing element of the first network device from a service routing element of the second network device a register message identifying a multicast source; and providing at least a portion of the register message from the service routing element of the first network device to the client routing element of the first network device in a manner that allows the third network device to learn the identity of the multicast source from the client routing element; wherein the client routing element replicates the register message to at least one of its anycast rendezvous point peers for delivery over a (*,G) multicast tree that was previously created in response to a (*,G) join message not designating any particular multicast source, where G denotes a multicast group. - View Dependent Claims (19)
-
-
20. A non-transitory processor-readable storage medium having embodied therein executable program code that when executed by a processor of the first network device causes the first network device:
-
to configure a service routing element of the first network device with a first anycast rendezvous point address such that the service routing element of the first network device is an anycast rendezvous point peer with at least a second network device in a service routing domain; to configure a client routing element of the first network device with a second anycast rendezvous point address such that the client routing element of the first network device is an anycast rendezvous point peer with at least a third network device in a client routing domain; to receive in the service routing element of the first network device from a service routing element of the second network device a register message identifying a multicast source; and to provide at least a portion of the register message from the service routing element of the first network device to the client routing element of the first network device in a manner that allows the third network device to learn the identity of the multicast source from the client routing element; wherein the first network device comprises a provider edge device spanning the service and client routing domains; and wherein the third network device comprises a customer edge device in the client routing domain.
-
Specification