Stitching a segment routing (SR) policy to a local SR policy for routing through a downstream SR domain
Systems and methods for enhancing Segment Routing (SR) protocols are provided for enabling the stitching of a remote SR policy to a local SR policy. A method can include obtaining a Segment Routing (SR) policy for routing a packet along a path in a downstream domain, the SR policy including at least a destination field and a color field, the destination field defining an end-point of the path in the downstream domain, the end-point representing a destination node or service instance, the color field defining the path in the downstream domain, and storing the SR policy in the database.
1. A Network Element (NE) arranged in an upstream domain of a network, the NE comprising:
a processing device,
a database, and
a memory device configured to store a computer program having instructions that, when executed, enable the processing device to
obtain, via an advertisement, a Segment Routing (SR) policy including a Binding Segment Identifier (BSID) for routing a packet along a path in a downstream domain, the SR policy including at least a destination field and a color field, the destination field defining an end-point of the path in the downstream domain, the end-point representing a destination node or service instance, the color field defining the path in the downstream domain, and
store the SR policy including the BSID in the database,
wherein the SR policy is for the downstream domain, separate from the upstream domain with the NE, wherein status of the downstream domain is unknown to the NE in the upstream domain, and wherein the advertisement includes the SR policy and the BSID associated therewith, and wherein the NE is a device located in the upstream domain and the NE uses the SR policy for the downstream domain to stitch SR policies between the upstream domain and the downstream domain without assistance from a higher level controller having knowledge of the NE and the downstream domain, and without a Path Computation Engine (PCE) configured to compute paths spanning across multiple Interior Gateway Protocol (IGP) areas or level.
2. The NE of claim 1 , wherein the SR policy further accompanies a source field identifying via the BSID a border node that straddles the upstream domain and the downstream domain.
3. The NE of claim 2 , wherein the instructions further enable the processing device to create a hierarchical SR policy having the BSID appended to an end of the hierarchical SR policy, wherein the hierarchical SR policy is configured for directing the packet to the border node before the border node routes the packet along the path in the downstream domain.
4. The NE of claim 3 , wherein the instructions further enable the processing device to select the hierarchical SR policy from one or more dynamic SR policies stored in the database for transmitting the packet along the path defined by the color field.
5. The NE of claim 3 , wherein the instructions enable the processing device to create the hierarchical SR policy based on a limited depth of a segment list of the hierarchical SR policy.
6. The NE of claim 3 , wherein the hierarchical SR policy is created for transmitting the packet from the NE to the end-point in the downstream domain without assistance from a higher level controller having knowledge of the NE and the end-point.
7. The NE of claim 1 , wherein the instructions further enable the processing device to perform an explicit path verification in the downstream domain, including checking validity of the BSID in the downstream domain related to the SR policy.
8. The NE of claim 1 , wherein the instructions further enable the processing device to use the SR Policy to forward packets/traffic to the end-point using the binding SID.
9. The NE of claim 1 , wherein the SR policy and the BSID are obtained via one of the Interior Gateway Protocol (IGP) and the Border Gateway Protocol (BGP).
10. The NE of claim 1 , wherein the BSID includes a value allocated by a Segment Routing Local Block (SRLB) associated with the downstream domain, the value is configured to identify and route traffic in the SR network.
11. The NE of claim 1 , wherein the NE is a border node.
12. The NE of claim 11 , wherein the instructions further enable the processing device to obtain status information regarding the integrity or liveness of the path in the downstream domain.
13. The NE of claim 12 , wherein the status information is related to the presence or absence of faults in the path in the downstream domain and/or changes to the topology of the downstream domain.
14. The NE of claim 12 , wherein the instructions further enable the processing device to update the database with the status information, and
provide the status information to one or more nodes in the upstream domain to enable each of the one or more nodes to
store the status information in a respective database, and
create a hierarchical SR policy based on one or more available SR policies stored in the respective database for communicating with one or more nodes in the downstream domain.
15. A non-transitory computer-readable medium configured to store computer logic having instructions that, when executed, cause one or more processing devices in a Network Element (NE) to:
obtain, via an advertisement, a Segment Routing (SR) policy including a Binding Segment Identifier (BSID) for routing a packet along a path in a downstream domain, the SR policy including at least a destination field and a color field, the destination field defining an end-point of the path in the downstream domain, the end-point representing a destination node or service instance, the color field defining the path in the downstream domain, and
store the SR policy including the BSID in the database,
wherein the SR policy is for the downstream domain, separate from the upstream domain with the NE, wherein status of the downstream domain is unknown to the NE in the upstream domain, and wherein the advertisement includes the SR policy and the BSID associated therewith, and wherein the NE is a device located in the upstream domain and the NE uses the SR policy for the downstream domain to stitch SR policies between the upstream domain and the downstream domain without assistance from a higher level controller having knowledge of the NE and the downstream domain, and without a Path Computation Engine (PCE) configured to compute paths spanning across multiple Interior Gateway Protocol (IGP) areas or level.
16. The non-transitory computer-readable medium of claim 15 , wherein the SR policy further accompanies a source field identifying a border node that straddles the upstream domain and the downstream domain.
17. The non-transitory computer-readable medium of claim 16 , wherein the instructions further cause the one or more processing devices to create a hierarchical SR policy having the BSID appended to an end of the hierarchical SR policy, wherein the hierarchical SR policy is configured for directing the packet to the border node before the border node routes the packet along the path in the downstream domain.
18. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the one or more processing devices to
represent the SR policy using the BSID, and
use the SR Policy to forward packets/traffic to the end-point using the binding SID.
19. A method comprising the steps of:
obtaining, via an advertisement, a Segment Routing (SR) policy including a Binding Segment Identifier (BSID) for routing a packet along a path in a downstream domain, the SR policy including at least a destination field and a color field, the destination field defining an end-point of the path in the downstream domain, the end-point representing a destination node or service instance, the color field defining the path in the downstream domain, and
storing the SR policy including the BSID in the database,
wherein the SR policy is for the downstream domain, separate from the upstream domain with the NE, wherein status of the downstream domain is unknown to the NE in the upstream domain, and wherein the advertisement includes the SR policy and the BSID associated therewith, and wherein the NE is a device located in the upstream domain and the NE uses the SR policy for the downstream domain to stitch SR policies between the upstream domain and the downstream domain without assistance from a higher level controller having knowledge of the NE and the downstream domain, and without a Path Computation Engine (PCE) configured to compute paths spanning across multiple Interior Gateway Protocol (IGP) areas or level.
20. The method of claim 19 , wherein the SR policy further accompanies a source field identifying a border node that straddles the upstream domain and the downstream domain and the BSID.