BACKGROUND

An internet protocol (IP) source node, such as an IPv6 node, can steer a payload packet through a specific path to a destination. For example, the source node may define the path as an ordered list of segments and may encode the path in an IPv6 routing header.

SUMMARY

According to some implementations, a method may include receiving, by a node, a first network topology message relating to a loosely routed segment of a network, wherein the first network topology message associates a first segment identifier (SID) with an address of a first terminal interface associated with the loosely routed segment; generating, by the node, a first entry in a segment translation table that associates the first SID with the address of the first terminal interface associated with the loosely routed segment; receiving, by the node, a second network topology message relating to a strictly routed segment of the network, wherein the second network topology message associates a second SID and an address of a second terminal interface associated with the strictly routed segment; generating, by the node, a second entry in the segment translation table that associates the second SID with the address of the second terminal interface associated with the strictly routed segment; receiving, by the node, an IP payload packet that has been encapsulated using an IPv6 transport header that has been extended with a compressed routing header (CRH) of variable length, wherein the CRH includes a list of SIDs that identify a set of nodes that the IP payload packet is to traverse while being routed through the network; determining, by the node and by referencing the list of SIDs, a next SID for the IP payload packet, wherein the next SID is associated with one of the first terminal interface or the second terminal interface; identifying, by the node and based on the segment translation table, an address associated with the next SID; and routing, by the node, the IP payload packet to the first terminal interface or the second terminal interface based on the address associated with the next SID.

According to some implementations, a node may include one or more memories and one or more processors to receive a first network topology message relating to a loosely routed segment of a network, wherein the first network topology message associates a first SID with an address of a first terminal interface associated with the loosely routed segment; generate a first entry in a segment translation table that associates the first SID with the address of the first terminal interface associated with the loosely routed segment; receive a second network topology message relating to a strictly routed segment of the network, wherein the second network topology message associates a second SID and an address of a second terminal interface associated with the strictly routed segment; and generate a second entry in the segment translation table that associates the second SID with the address of the second terminal interface associated with the strictly routed segment, wherein the segment translation table is to be used to route an IP payload packet that has been encapsulated using an IPv6 transport header that has been extended with a CRH of variable length, wherein the CRH includes a list of SIDs that identify a set of nodes that the IP payload packet is to traverse while being routed through the network.

According to some implementations, a non-transitory computer-readable medium may store one or more instructions that, when executed by one or more processors of a node, may cause the one or more processors to receive a network topology message that identifies one of a first association of a first SID, relating to a loosely routed segment of a network, and an address of a first terminal interface associated with the loosely routed segment, or a second association of a second SID, relating to a strictly routed segment of the network, and an address of a second terminal interface associated with the strictly routed segment; generate an entry in a segment translation table based on the first association identified in the network topology message or the second association identified in the network topology message; and route, according to the segment translation table, an IP payload packet that has been encapsulated using an IPv6 transport header that has been extended with a CRH of variable length, wherein the CRH includes a list of SIDs that identify a set of nodes that the IP payload packet is to traverse while being routed through the network.

