%% You should probably cite draft-ietf-spring-segment-routing-mpls instead of this I-D.
@techreport{filsfils-spring-segment-routing-mpls-00,
    number =    {draft-filsfils-spring-segment-routing-mpls-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-filsfils-spring-segment-routing-mpls/00/},
    author =    {Clarence Filsfils and Stefano Previdi and Ahmed Bashandy 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 Edward Crabbe},
    title =     {{Segment Routing with MPLS data plane}},
    pagetotal = 11,
    year =      2013,
    month =     oct,
    day =       20,
    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. The Segment Routing architecture can be directly applied to the MPLS data plane with no change in the forwarding plane. This drafts describes how Segment Routing operates on top of the MPLS data plane.},
}