%% You should probably cite draft-ietf-6man-segment-routing-header instead of this I-D. @techreport{previdi-6man-segment-routing-header-00, number = {draft-previdi-6man-segment-routing-header-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-previdi-6man-segment-routing-header/00/}, author = {Stefano Previdi and Clarence Filsfils and Brian Field and Ida Leung}, title = {{IPv6 Segment Routing Header (SRH)}}, pagetotal = 22, year = 2014, month = mar, day = 6, abstract = {Segment Routing (SR) allows a node to steer a packet through a controlled set of instructions, called segments, by prepending a SR header to the packet. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any path (topological, or application/service based) while maintaining per-flow state only at the ingress node to the SR domain. The Segment Routing architecture can be applied to the IPv6 data plane with the addition of a new type of Routing Extension Header. This draft describes the Segment Routing Extension Header Type and how it is used by SR capable nodes.}, }