Optimized multicast transport migration procedures
The present technology provides solutions for optimizing communications between nodes and can include receiving, by a first node from a second node, an advertisement indicating an advertisement transport protocol supported by the second node, where the first node supports a plurality of transport protocols, and the advertisement transport protocol is one of the plurality of transport protocols, where the first node and the second node are nodes of a border gateway protocol (BGP) community, receiving, by the first node, from a requesting node a request to join the BGP community, where the request includes an attribute indicating a request transport protocol supported by the requesting node, allocating, by the first node and based on the attribute, a resource for the request transport protocol supported by the requesting node, and providing, by the first node, a notification to the second node indicating allocation of the resource for the request transport protocol.
1 . A method for optimizing communications between nodes, the method comprising:
receiving, by a first node, an advertisement indicating an advertisement transport protocol supported by a second node, wherein the first node supports a plurality of transport protocols, and the advertisement transport protocol is one of the plurality of transport protocols, wherein the first node and the second node are edge nodes of a border gateway protocol (BGP) community;
receiving, by the first node, from a requesting node through the second node a request to join the BGP community and access a resource, wherein the request includes an attribute indicating a request transport protocol supported by the requesting node, and wherein the first node and second node are part of the BGP community and the requesting node is not part of the BGP community;
allocating, by the first node and based on the attribute, the resource for the request transport protocol supported by the requesting node;
providing, by the first node, a notification to one or more intermediate nodes and the second node indicating allocation of the resource for the request transport protocol; and
receiving, by the first node, an underlay join request for the request transport protocol enabling traffic to flow from the first node to the second node.
2 . The method of claim 1 , wherein providing the notification to the second node includes sending the notification to a route reflector or a rendezvous point.
3 . The method of claim 1 , further comprising:
sending, by the first node through a third node supporting the request transport protocol supported by the requesting node, the resource to the requesting node.
4 . The method of claim 1 , wherein the second node does not support the request transport protocol supported by the requesting node.
5 . The method of claim 1 , wherein the second node supports a second plurality of transport protocols.
6 . The method of claim 1 , wherein the second node is configured to receive a communication by a first transport protocol from the first node and send a second communication by a second transport protocol to the requesting node.
7 . The method of claim 6 , wherein the second communication is the communication translated to be sent over the second transport protocol.
8 . The method of claim 1 , wherein the resource is a website configured to be multicasted by the first node.
9 . One or more non-transitory computer-readable media comprising computer-readable instructions stored thereon, wherein the computer-readable instructions, when executed by one or more processors, cause the one or more processors to:
receive, by a first node, an advertisement indicating an advertisement transport protocol supported by a second node, wherein the first node supports a plurality of transport protocols, and the advertisement transport protocol is one of the plurality of transport protocols, wherein the first node and the second node are edge nodes of a border gateway protocol (BGP) community;
receive, by the first node, from a requesting node through the second node a request to join the BGP community and access a resource, wherein the request includes an attribute indicating a request transport protocol supported by the requesting node, and wherein the first node and second node are part of the BGP community and the requesting node is not part of the BGP community;
allocate, by the first node and based on the attribute, the resource for the request transport protocol supported by the requesting node;
provide, by the first node, a notification to one or more intermediate nodes and the second node indicating allocation of the resource for the request transport protocol; and
receiving, by the first node, an underlay join request for the request transport protocol enabling traffic to flow from the first node to the second node.
10 . The one or more non-transitory computer-readable media of claim 9 , wherein providing the notification to the second node includes sending the notification to a route reflector or a rendezvous point.
11 . The one or more non-transitory computer-readable media of claim 9 , wherein the execution of the computer-readable instructions, by the one or more processors, cause the one or more processors to:
send, by the first node through a third node supporting the request transport protocol supported by the requesting node, the resource to the requesting node.
12 . The one or more non-transitory computer-readable media of claim 9 , wherein the second node does not support the request transport protocol supported by the requesting node.
13 . The one or more non-transitory computer-readable media of claim 9 , wherein the second node supports a second plurality of transport protocols.
14 . The one or more non-transitory computer-readable media of claim 9 , wherein the second node is configured to receive a communication by a first transport protocol from the first node and send a second communication by a second transport protocol to the requesting node.
15 . The one or more non-transitory computer-readable media of claim 14 , wherein the second communication is the communication translated to be sent over the second transport protocol.
16 . The one or more non-transitory computer-readable media of claim 9 , wherein the resource is a website configured to be multicasted by the first node.
17 . A system comprising:
one or more processors; and
one or more memories configured to store computer-readable instructions thereon, which when executed by the one or more processors, cause the one or more processors to:
receive, by a first node, an advertisement indicating an advertisement transport protocol supported by a second node, wherein the first node supports a plurality of transport protocols, and the advertisement transport protocol is one of the plurality of transport protocols, wherein the first node and the second node are edge nodes of a border gateway protocol (BGP) community;
receive, by the first node, from a requesting node through the second node a request to join the BGP community and access a resource, wherein the request includes an attribute indicating a request transport protocol supported by the requesting node, and wherein the first node and second node are part of the BGP community and the requesting node is not part of the BGP community;
allocate, by the first node and based on the attribute, the resource for the request transport protocol supported by the requesting node;
provide, by the first node, a notification to one or more intermediate nodes and the second node indicating allocation of the resource for the request transport protocol; and
receive, by the first node, an underlay join request for the request transport protocol enabling traffic to flow from the first node to the second node.
18 . The system of claim 17 , wherein providing the notification to the second node includes sending the notification to a route reflector or a rendezvous point.
19 . The system of claim 17 , wherein the one or more processors are configured to execute the computer-readable instructions to:
send, by the first node through a third node supporting the request transport protocol supported by the requesting node, the resource to the requesting node.
20 . The system of claim 17 , wherein the second node does not support the request transport protocol supported by the requesting node.