Computing forward and reverse paths and checking the liveness thereof
Systems and methods for computing forward and reverse paths and checking the liveness, keep-alive status, or continuity of the forward and reverse paths are provided. A method, according to one implementation, includes the step of creating one or more messages related to a computation of a forward path from a head-end node to a tail-end node and a computation of a reverse path from the tail-end node to the head-end node. The method also includes the step of adding a data object to the one or more messages, the data object including an intent to check the liveness of the forward path and reverse path.
1. A system comprising:
a processing device, and
a memory device configured to store a computer program having instructions that, when executed, enable the processing device to
create one or more messages related to a computation of a forward path from a head-end node to a tail-end node and a computation of a reverse path from the tail-end node to the head-end node, and
add a data object to the one or more messages, the data object including an intent to check the liveness of the forward path and the reverse path, wherein the data object includes Path Setup Type (PST) Type-Length-Value (TLV) information having one or more flags for defining (1) whether the forward path and the reverse path traverse the same hops or utilize independent routes and (2) a transport type of the reverse path.
2. The system of claim 1 , wherein the instructions further enable the processing device to automatically compute the forward path and the reverse path, and wherein the forward path and the reverse path traverse multiple administrative domains, network domains, or autonomous systems separating the head-end node from the tail-end node by one or more border nodes, transition points, or gateways.
3. The system of claim 1 , wherein checking the liveness of the forward path and the reverse path is defined by one or more protocols associated with Bi-directional Forwarding Detection (BFD) and Seamless BFD (S-BFD).
4. The system of claim 3 , wherein the data object is an S-BFD object and includes discriminator values for identifying the head-end node and tail-end node.
5. The system of claim 1 , wherein the computation of the forward path and the reverse path is defined by one or more protocols associated with the Path Computation Element Protocol (PCEP).
6. The system of claim 1 , wherein the transport type is related to one of (1) a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP), (2) Segment Routing (SR), or (3) Resource Reservation Protocol (RSVP).
7. The system of claim 1 , wherein the instructions further enable the processing device to configure the forward path and the reverse path with the same transport type of a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP).
8. The system of claim 1 , wherein the transport type is related to Segment Routing (SR), and wherein the one or more messages include a list of Segment Identifiers (SIDs) for defining the forward path and the reverse path.
9. The system of claim 1 , wherein the data object defines the forward path and the reverse path utilize the independent routes.
10. The system of claim 1 , wherein the transport type is related to Resource Reservation Protocol (RSVP), and wherein the one or more messages include Explicit Route Objects (EROs).
11. The system of claim 1 , wherein the system is a Path Computation Client (PCC) associated with the head-end node and is configured to:
initiate a Request to compute the forward path and the reverse path and to check the liveness of the forward path and the reverse path, and
send the Request to a server arranged in a control plane for coordinating path computation and path liveness checking with the head-end node and tail-end node.
12. The system of claim 1 , wherein the system is a Path Computation Element (PCE) associated with a server arranged in a control plane and is configured to:
send a first Initiate packet regarding the forward path to the head-end node via the control plane, and
send a second Initiate packet regarding the reverse path to the tail-end node via the control plane.
13. The system of claim 12 , wherein the PCE is further configured to:
receive Report packets from the head-end node and tail-end node via the control plane, and
send Update packets to the head-end node and tail-end node via the control plane.
14. A non-transitory computer-readable medium configured to store computer logic having instructions that, when executed, cause one or more processing devices to:
create one or more messages related to a computation of a forward path from a head-end node to a tail-end node and a computation of a reverse path from the tail-end node to the head-end node, and
add a data object to the one or more messages, the data object including an intent to check the liveness of the forward path and the reverse path, wherein the data object includes Path Setup Type (PST) Type-Length-Value (TLV) information having one or more flags for defining (1) whether the forward path and the reverse path traverse the same hops or utilize independent routes and (2) a transport type of the reverse path.
15. The non-transitory computer-readable medium of claim 14 , wherein the instructions further cause the one or more processing devices to automatically compute the forward path and the reverse path, and wherein the forward path and the reverse path traverse multiple administrative domains, network domains, or autonomous systems separating the head-end node from the tail-end node by one or more border nodes, transition points, or gateways.
16. The non-transitory computer-readable medium of claim 14 , wherein checking the liveness of the forward path and the reverse path is defined by one or more protocols associated with Seamless BFD (S-BFD), and wherein the data object is an S-BFD object and includes discriminator values for identifying the head-end node and tail-end node.
17. The non-transitory computer-readable medium of claim 14 , wherein the computation of the forward path and the reverse path is defined by one or more protocols associated with the Path Computation Element Protocol (PCEP).
18. The non-transitory computer-readable medium of claim 14 , wherein the transport type is related to one of (1) a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP), (2) Segment Routing (SR), or (3) Resource Reservation Protocol (RSVP).
19. A method comprising the steps of:
creating one or more messages related to a computation of a forward path from a head-end node to a tail-end node and a computation of a reverse path from the tail-end node to the head-end node, and
adding a data object to the one or more messages, the data object including an intent to check the liveness of the forward path and the reverse path, wherein the data object includes Path Setup Type (PST) Type-Length-Value (TLV) information having one or more flags for defining (1) whether the forward path and the reverse path traverse the same hops or utilize independent routes and (2) a transport type of the reverse path.
20. The method of claim 19 , wherein the transport type is related to one of (1) a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP), (2) Segment Routing (SR), or (3) Resource Reservation Protocol (RSVP).