Resolving label depth and protection in segment routing
A source node in a first domain in a multi-domain network includes a plurality of ports; and switching circuitry configured to forward packets between the plurality of ports, wherein the source node is configured to, for a packet destined for a destination node in another domain in the multi-domain network, add a list of Segment Identifiers (SIDs) to the packet for loose source-based routing from the source node, through the first domain, and to the another domain, and forward the packet via a port of the plurality of ports and with the list of SIDs, wherein the list of SIDs includes at least one SID representing both an anycast SID and a binding SID. The SID is associated with an anycast group that includes a plurality of nodes, and with a binding segment in the second domain, the binding segment includes a different SID list for each node of the plurality of nodes.
1. A source node in a first domain in a multi-domain network, the source node comprising:
a plurality of ports; and
switching circuitry configured to forward packets between the plurality of ports,
wherein the source node is configured to
for a packet destined for a destination node in another domain in the multi-domain network, add a list of Segment Identifiers (SIDs) to the packet for loose source-based routing from the source node, through the first domain, and to the another domain, and
forward the packet via a port of the plurality of ports and with the list of SIDs,
wherein the list of SIDs includes at least one SID representing both an anycast SID and a binding SID, and wherein the at least one SID is a single label that causes performance of functionality of both the anycast SID and the binding SID.
2. The source node of claim 1 , wherein the at least one SID is associated with an anycast group that includes a plurality of nodes in a second domain, connected to the first domain.
3. The source node of claim 2 , wherein the first domain is configured to send the packet with the at least one SID to a closest node of the plurality of nodes.
4. The source node of claim 2 , wherein the at least one SID is associated with a binding segment in the second domain, and the binding segment includes a different SID list for each node of the plurality of nodes.
5. The source node of claim 2 , wherein the second domain is the another domain.
6. The source node of claim 2 , wherein the second domain is a transit domain between the first domain and the another domain.
7. The source node of claim 2 , wherein the plurality of nodes are border nodes that are dual homed between the first domain and the second domain.
8. A border node in a multi-domain network comprising:
a plurality of ports; and
switching circuitry configured to forward packets between the plurality of ports,
wherein the border node is configured to
receive a packet from a first domain, the packet is destined for a destination node in a same domain as the border node or another domain in the multi-domain network,
pop a Segment Identifier (SID) from the packet, wherein the SID represents both an anycast SID and a binding SID, the packet being sent to the border node from the first domain based on the presence of the border node in an anycast group associated with the SID, wherein the SID is a single label that causes performance of functionality of both the anycast SID and the binding SID,
add one or more SIDs to the packet based on a policy associated with a binding segment for the SID, and
forward the packet with the one or more SIDs.
9. The border node of claim 8 , wherein the SID is associated with the anycast group that includes a plurality of nodes in the same domain or another domain, connected to the first domain.
10. The border node of claim 9 , wherein the first domain is configured to send the packet with the SID to a closest node in the same domain.
11. The border node of claim 9 , wherein the SID is associated with the binding segment in the same domain or another domain, and the binding segment includes a different SID list for the border node from another node of the plurality of nodes.
12. The border node of claim 9 , wherein the border node is in the same domain as the destination node.
13. The border node of claim 9 , wherein the border node is in a transit domain between the first domain and a domain containing the destination node.
14. The border node of claim 9 , wherein the border node is dual homed between the first domain and the same domain or another domain, with one or more nodes of the plurality of nodes.
15. A method comprising:
for a packet destined for a destination node in another domain in a multi-domain network, adding a list of Segment Identifiers (SIDs) to the packet for loose source-based routing from a source node, through a first domain, and to the another domain; and
forwarding the packet via a port with the list of SIDs,
wherein the list of SIDs includes at least one SID representing both an anycast SID and a binding SID, and wherein the at least one SID is a single label that causes performance of functionality of both the anycast SID and the binding SID.
16. The method of claim 15 , further comprising
receiving the packet from the first domain at a border node;
popping the at least one SID; and
adding one or more SIDs at the border node based on a policy at the border node.
17. The method of claim 15 , wherein the at least one SID is associated with an anycast group that includes a plurality of nodes in a second domain, connected to the first domain.
18. The method of claim 17 , wherein the first domain is configured to send the packet with the at least one SID to a closest node of the plurality of nodes.
19. The method of claim 17 , wherein the at least one SID is associated with a binding segment in the second domain, and the binding segment includes a different SID list for each node of the plurality of nodes.
20. The method of claim 17 , further comprising
responsive to a failure associated with one of the plurality of nodes, forwarding the packet to another node in the anycast group.