%% You should probably cite rfc8660 instead of this I-D. @techreport{ietf-spring-segment-routing-mpls-02, number = {draft-ietf-spring-segment-routing-mpls-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-mpls/02/}, author = {Clarence Filsfils and Stefano Previdi and Ahmed Bashandy and Bruno Decraene and Stephane Litkowski and Martin Horneffer and Rob Shakir and Jeff Tantsura and Edward Crabbe}, title = {{Segment Routing with MPLS data plane}}, pagetotal = 14, year = 2015, month = oct, day = 17, abstract = {Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SR domain. Segment Routing can be directly applied to the MPLS architecture with no change in the forwarding plane. This drafts describes how Segment Routing operates on top of the MPLS data plane.}, }