Abstract: In one embodiment, a Segment Routing network node provides efficiencies in processing and communicating Internet Protocol packets in a network. An Internet Protocol (IP) packet, possibly a Segment Routing packet, is received by a node in a network, which updates the packet according to a corresponding Segment Routing Policy, that includes an ordered list of Segment Identifiers comprising, in first-to-last order, a first Segment Identifier followed by one or more subsequent Segment Identifiers. The updating of the packet includes setting the Destination Address to the first Segment Identifier, and adding said one or more subsequent Segment Identifiers, but not the first Segment Identifier, in a first Segment Routing Header. The updated packet is sent into the network without the first Segment Identifier being added to a Segment Routing Header in response to the Segment Routing Policy.

Abstract: The present technology is directed to a scalable solution for end-to-end performance delay measurement for Segment Routing Policies on both SR-MPLS and SRv6 data planes. The scalability of the solution stems from the use of distributed PM sessions along SR Policy ECMP paths. This is achieved by dividing the SR policy into smaller sections comprised of SPT trees or sub-paths, each of which is associated with a Root-Node. Downstream SID List TLVs may be used in Probe query messages for signaling SPT information to the Root-Nodes Alternatively, this SPT signaling may be accomplished by using a centralized controller. Root-Nodes are responsible for dynamically creating PM sessions and measuring delay metrics for their associated SPT tree section. The root-nodes then send the delay metrics for their local section to an ingress PE node or to a centralized controller using delay metric TLV field of the response message.

Abstract: In one embodiment, a network comprises a first forwarding domain using a first data plane forwarding protocol and a second forwarding domain using a second data plane forwarding protocol different than the first data forwarding plane forwarding protocol. The first forwarding domain includes a first path node and a particular border node. The second forwarding domain includes a second path node and the particular border node. The particular border node performs Segment Routing or other protocol interworking between the different data plane forwarding domains, such as for transporting packets through a different forwarding domain or translating a packet to use a different data forwarding protocol. These forwarding domains typically include Segment Routing (SR) and SR-Multiprotocol Label Switching (SR-MPLS). Paths through the network are determined by a Path Computation Engine and/or based on route advertisements such associated with Binding Segment Identifiers (BSIDs) (e.g.

Abstract: In one embodiment, Ethernet Virtual Private Network (EVPN) is implemented using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) underlay network and SRv6-enhanced Border Gateway Protocol (BGP) signaling. A particular route associated with a particular Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) Segment Identifier (SID) is advertised in a particular route advertisement message of a routing protocol (e.g., BGP). The SID includes encoding representing a particular Ethernet Virtual Private Network (EVPN) Layer 2 (L2) flooding Segment Routing end function of the particular router and a particular Ethernet Segment Identifier (ESI), with the particular SID including a routable prefix to the particular router. The particular router receives a particular packet including the particular SID; and in response, the particular router performs the particular EVPN end function on the particular packet.

Abstract: The present technology provides a system and method for implementing targeted collection of in-situ Operation, Administration and Maintenance data from select nodes in a Segment Routing Domain. The selection is programmable and is implemented by setting an iOAM bit in the function arguments field of a Segment Identifier. In this way only the nodes associated with local Segment Identifiers (Function field of a Segment Identifier) with an iOAM argument bit are directed to generate iOAM data. The iOAM data generated by target nodes may be stored in TLV field of the segment routing header. The Segment Routing packet is then decapsulated at a Segment Routing egress node and the Header information with the collected iOAM data is sent to a controller entity for further processing, analysis and/or monitoring.

Abstract: Disclosed is an apparatus and method for segment routing using a remote forwarding adjacency identifier. In one embodiment, a first node in a network receives a packet, wherein the packet is received with a first segment-ID and another segment ID attached thereto. The first node detaches the first and the other segment IDs from the packet. Then the first node attaches a first label to the packet. Eventually, the first node forwards the packet with the attached first label directly to a second node in the network. In one embodiment, the other segment ID corresponds to a forwarding adjacency or tunnel label switched path between the first node and another node.

Abstract: The present technology is directed to a system and method for implementing network resource partitioning and Quality of Service (QoS) separation through network slicing. Embodiments of the present invention describe scalable network slicing method based on defining Segment Routing Flexible Algorithm to represent a network slice and assigning a distinct QoS policy queue to each of the Flexible Algorithms configured on a network node. Therefore, scalable network slice based queuing is implemented wherein a single packet processing queue is assigned to each Flex-Algorithm based network slice. QoS policy queue may be implemented in a hierarchical fashion by differentiation between flow packets in a single QoS policy queue based on value of experimental bits in the header.

Abstract: In one embodiment, a segment routing and tunnel exchange provides packet forwarding efficiencies in a network, including providing an exchange between a segment routing domain and a packet tunnel domain. One application includes the segment routing and tunnel exchange interfacing segment routing packet forwarding (e.g., in a Evolved Packet Core (EPC) and/or 5-G user plane) and packet tunnel forwarding in access networks (e.g., replacing a portion of a tunnel between an access node and a user plane function for accessing a corresponding data network). In one embodiment, a network provides mobility services using a segment routing data plane that spans segment routing and tunnel exchange(s) and segment routing-enabled user plane functions. One embodiment uses the segment routing data plane without any modification to a (radio) access network (R)AN (e.g., Evolved NodeB, Next Generation NodeB) nor to user equipment (e.g., any end user device).

Abstract: Techniques for in-situ passive performance measurement are described. In one embodiment, a method includes receiving a data packet at a first network element, determining whether measurement information is to be collected for the data packet, providing one or more measurement fields for the data packet based on a determination that measurement information is to be collected for the data packet in which at least one measurement field identifies a measurement type, and forwarding the data packet to a second network element. The method further includes determining, by the second network element, the measurement type for the data packet, and performing one or more actions based on the measurement type.

Abstract: The present technology is directed to a scalable solution for end-to-end performance delay measurement for Segment Routing Policies on both SR-MPLS and SRv6 data planes. The scalability of the solution stems from the use of distributed PM sessions along SR Policy ECMP paths. This is achieved by dividing the SR policy into smaller sections comprised of SPT trees or sub-paths, each of which is associated with a Root-Node. Downstream SID List TLVs may be used in Probe query messages for signaling SPT information to the Root-Nodes Alternatively, this SPT signaling may be accomplished by using a centralized controller. Root-Nodes are responsible for dynamically creating PM sessions and measuring delay metrics for their associated SPT tree section. The root-nodes then send the delay metrics for their local section to an ingress PE node or to a centralized controller using delay metric TLV field of the response message.

Abstract: In one embodiment, a service chain data packet is instrumented as it is communicated among network nodes in a network providing service-level and/or networking operations visibility. The service chain data packet includes a particular header identifying a service group defining one or more service functions, and is a data packet and not a probe packet. A network node adds networking and/or service-layer operations data to the particular service chain data packet, such as, but not limited to, in the particular header. Such networking operations data includes a performance metric or attribute related to the transport of the particular service chain packet in the network. Such service-layer operations data includes a performance metric or attribute related to the service-level processing of the particular service chain data packet in the network.

Abstract: An apparatus and method for path creation element driven dynamic setup of forwarding adjacencies and explicit path. In one embodiment of the method, a node receives an instruction to create a tunnel between the node and another node. The node creates or initiates the creation of the tunnel in response to receiving the instruction, wherein the tunnel comprises a plurality of nodes in data communication between the node and the other node. The node maps a first identifier (ID) to information relating to the tunnel. The node advertises the first ID to other nodes in a network of nodes.

Abstract: Systems, methods, and computer-readable media for providing multi-cloud connectivity. A method can involve adding a new virtual private cloud (VPC) to a multi-cloud environment including a private network and VPCs connected to the private network via a segment routing (SR) domain and respective virtual routers on the VPCs and the private network. The method can involve deploying a new virtual router on the new VPC, registering the new virtual router at a BGP controller in the multi-cloud environment, and receiving, at the BGP controller, topology information from the new virtual router. The method can further involve identifying routes in the multi-cloud environment based on paths computed based on the topology information, sending, to the new virtual router, routing information including the routes, SR identifiers and SR policies, and based on the routing information, providing interconnectivity between the private network, the VPCs, and the new VPC.

Abstract: Resource rationing for network slices in segment routing networks may be provided. A network slice may be created in a communication network. A portion of network resource may be dedicated to the network slice. The dedicated portion of network resource may be bound to the network slice using a segment identifier. The segment identifier may be advertised to the communication network. Data packets associated with the network slice may be routed using the dedicated portion of network resource.

Abstract: In one embodiment, a Segment Routing network node provides processing and network efficiencies in protecting Internet Protocol version 6 (IPv6) Segment Routing (SRv6) packets and functions using Security Segment Identifiers, which are included in Segment Lists of a Segment Routing Header of a SRv6 packet. The Security Segment Identifier provides, inter alia, origin authentication, integrity of information in one or more headers of the packet, and/or anti-replay protection. In one embodiment, a Security Segment Identifier includes a value determined based on a secured portion of the packet. A typically secured portion includes the Source and Destination Addresses, one or more Segment Identifiers in a Segment List and the Segments Left value. In one embodiment, the Destination Address and/or a Segment Identifier in the Segment List includes and an anti-replay value (e.g., sequence number or portion thereof) which is also in the secured portion of the packet.

Abstract: In one embodiment, segment routing network processing of packets is performed, including using segment routing packet policies and functions providing segment routing processing signaling and packet forwarding efficiencies in a network. A segment routing node signals to another segment routing node using a signaled segment identifier in a segment list of a segment routing packet with the segments left identifying a segment list element above the signaled segment identifier. A downstream segment routing node receives the segment routing packet, obtains this signaled segment identifier, and performs processing of one or more packets based thereon. In one embodiment, a provider edge node replaces its own segment identifier in a received customer packet, with a downstream customer node using the replaced (signaling) segment identifier (of a provider edge node/segment routing function) for accessing a return path through the provider network.

Abstract: In one embodiment, a Segment Routing gateway receives Segment Routing packets encapsulating native packets. The Segment Routing gateway stores the Segment Routing encapsulating headers. The native packets are communicated to a service function (or other device). Upon return, Segment Routing packets are generated including the returned native packets using correspondingly stored Segment Routing encapsulating headers, possibly updated with new policies. Segment Routing includes, but is not limited to, SRv6 and SR-MPLS. In one embodiment, the native packet is sent from a physical interface of the SR gateway to the service function, and returned to the SR gateway on one of its physical interface(s). In one embodiment, shared storage is accessible to both the SR gateway and the service function (or other device), so references (e.g., memory locations or pointers) are communicated between the SR gateway and the service function (or other device).

Abstract: In one embodiment, Ethernet Virtual Private Network (EVPN) is implemented using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) underlay network and SRv6-enhanced Border Gateway Protocol (BGP) signaling. A particular route associated with a particular Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) Segment Identifier (SID) is advertised in a particular route advertisement message of a routing protocol (e.g., BGP). The SID includes a locator of a particular router and a function encoding representing a particular EVPN end function of the particular router, with the particular SID including a routable prefix to the particular router. The particular router receives a particular packet including the particular SID; and in response, the particular router performs the particular EVPN end function on the particular packet. In one embodiment, the particular packet includes a Segment Routing Header (SRH) including the particular SID as the currently active SID.

Abstract: A system and method are disclosed for using segment routing (SR) in native IP networks. The method involves receiving a packet. The packet is an IP packet and includes an IP header. The method also involves updating the packet. Updating the packet involves writing information, including a segment routing segment identifier, to the destination address of the packet.

Abstract: A method is performed at a source node in a network of nodes configured with a link state protocol, and in which at least some of the nodes are enabled for multiprotocol label switching (MPLS). The node discovers and stores a link state topology representing the nodes of the network, links between the nodes, path-costs for the links, and whether each link is enabled or not enabled for MPLS. The node determines one or more shortest paths from the source node to a destination node among the nodes based on traversing the link state topology and, while the node traverses the link state topology, detects whether each shortest path supports or does not support MPLS end-to-end dataplane continuity. The node programs an IP dataplane with each shortest path, and programs an MPLS dataplane with ones of the one or more shortest paths that support the end-to-end MPLS continuity.