Abstract: In one embodiment, new Segment Routing capabilities are used in the steering of packets through Segment Routing nodes in a network. A Segment List includes a set of one or more Segment List (SL) Groups, each of which identifies one or more Segments contiguously or non-contiguously stored in the Segment List (or stored across multiple Segment Lists) of a Segment Routing packet. Each SL Group typically includes one Segment that is encoded as a Segment Identifier, and may include Segments that are Extended Values. The steering order of SL Groups is not required to be the same order as they are listed in the Segment List, as the value of Segments Left may be increased, remain the same, or decreased (possibly to skip a next SL Group) and possibly based on the result of an evaluation of a conditional expression.

Abstract: In one embodiment, a third-party client network access device sends Internet Protocol (IP) encapsulating packets with a predetermined destination address of a node of the network client service provider (NCSP), with these IP encapsulating packets encapsulating original data packets. These IP encapsulating packets are communicated through the ISP network being used by the NCSP in providing its network services. The predetermined destination address, which is typically also a segment identifier, causes network service processing (e.g., according to a corresponding segment routing function) of the received packet by the node of the NCSP. This processing typically includes creating a segment routing packet encapsulating the original packet (extracted from the received IP encapsulating packet) with its segment list(s) being populated with segment identifier(s) according to a current NCSP segment routing policy reflective of a sequence of forwarding and service chaining operations of the NCSP service offering.