%% You should probably cite draft-filsfils-spring-segment-routing-use-cases instead of this I-D. @techreport{filsfils-rtgwg-segment-routing-use-cases-02, number = {draft-filsfils-rtgwg-segment-routing-use-cases-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-filsfils-rtgwg-segment-routing-use-cases/02/}, author = {Clarence Filsfils and Pierre Francois and Stefano Previdi and Bruno Decraene and Stephane Litkowski and Martin Horneffer and Igor Milojevic and Rob Shakir and Saku Ytti and Wim Henderickx and Jeff Tantsura and Sriganesh Kini and Edward Crabbe}, title = {{Segment Routing Use Cases}}, pagetotal = 36, year = 2013, month = oct, day = 21, abstract = {Segment Routing (SR) leverages the source routing and tunneling paradigms. 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 of the SR domain. The Segment Routing architecture can be directly applied to the MPLS dataplane with no change on the forwarding plane. It requires minor extension to the existing link-state routing protocols. Segment Routing can also be applied to IPv6 with a new type of routing extension header.}, }