Handling diversity constraints with Segment Routing and centralized PCE
A method implemented in a network element includes, for a service, receiving a Segment Identifier (SID) list and an explicit list for an intended path in a Segment Routing network; expanding the SID list and comparing the expanded SID list to the explicit list; and setting the intended path as either valid or invalid based on the comparing. The intended path can be a primary path, and the steps can further include receiving a SID list and an explicit list for a backup path in the Segment Routing network. The steps can further include switching to the backup path responsive to a failure on the primary path, and switching back to the primary path responsive to it being valid.
1. A non-transitory computer-readable medium having instructions stored thereon for programming a network element to perform steps of:
for a service, receiving a Segment Identifier (SID) list and an explicit list for an intended path in a Segment Routing network;
expanding the SID list and comparing the expanded SID list to the explicit list; and
setting the intended path as either valid or invalid based on the comparing where the intended path is invalid when the expanded SID list is not identical to the explicit list such that the intended path does not match a path from the expanded SID list.
2. The non-transitory computer-readable medium of claim 1 , wherein the intended path is a primary path, and wherein the steps further include
receiving a SID list and an explicit list for a backup path in the Segment Routing network.
3. The non-transitory computer-readable medium of claim 2 , wherein the steps further include
switching to the backup path responsive to invalidity of the primary path; and
switching back to the primary path responsive to it being valid.
4. The non-transitory computer-readable medium of claim 1 , wherein the receiving is from a Path Computation Element (PCE).
5. The non-transitory computer-readable medium of claim 1 , wherein the receiving is by the network element which is a head-end router for the service.
6. The non-transitory computer-readable medium of claim 1 , wherein the SID list is compressed and the explicit list includes every network element for the intended path.
7. The non-transitory computer-readable medium of claim 1 , wherein the intended path is valid when the expanded SID matches the explicit list.
8. A method implemented in a network element comprising steps of:
for a service, receiving a Segment Identifier (SID) list and an explicit list for an intended path in a Segment Routing network;
expanding the SID list and comparing the expanded SID list to the explicit list; and
setting the intended path as either valid or invalid based on the comparing where the intended path is invalid when the expanded SID list is not identical to the explicit list such that the intended path does not match a path from the expanded SID list.
9. The method of claim 8 , wherein the intended path is a primary path, and wherein the steps further include
receiving a SID list and an explicit list for a backup path in the Segment Routing network.
10. The method of claim 9 , wherein the steps further include
switching to the backup path responsive to invalidity of the primary path; and
switching back to the primary path responsive to it being valid.
11. The method of claim 8 , wherein the receiving is from a Path Computation Element (PCE).
12. The method of claim 8 , wherein the receiving is by the network element which is a head-end router for the service.
13. The method of claim 8 , wherein the SID list is compressed and the explicit list includes every network element for the intended path.
14. The method of claim 8 , wherein the intended path is valid when the expanded SID matches the explicit list.
15. A network element comprising circuitry configured to:
for a service, receive a Segment Identifier (SID) list and an explicit list for an intended path in a Segment Routing network,
expand the SID list and comparing the expanded SID list to the explicit list, and
set the intended path as either valid or invalid based on the comparing where the intended path is invalid when the expanded SID list is not identical to the explicit list such that the intended path does not match a path from the expanded SID list.
16. The network element of claim 15 , wherein the intended path is a primary path, and wherein the circuitry is further configured to
receive a SID list and an explicit list for a backup path in the Segment Routing network.
17. The network element of claim 16 , wherein the circuitry is further configured to
switch to the backup path responsive to invalidity of the primary path, and
switch back to the primary path responsive to it being valid.
18. The network element of claim 15 , wherein the SID list and the explicit list is received from a Path Computation Element (PCE).
19. The network element of claim 15 , wherein the SID list and the explicit list is received by the network element which is a head-end router for the service.
20. The network element of claim 15 , wherein the SID list is compressed and the explicit list includes every network element for the intended path.