%% You should probably cite rfc8754 instead of this I-D.
@techreport{ietf-6man-segment-routing-header-08,
    number =    {draft-ietf-6man-segment-routing-header-08},
    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-6man-segment-routing-header/08/},
    author =    {Stefano Previdi and Clarence Filsfils and Syed Kamran Raza and Darren Dukes and John Leddy and Brian Field and Daniel Voyer and Daniel Bernier and Satoru Matsushima and Ida Leung and Jen Linkova and Ebben Aries and Tomoya Kosugi and Éric Vyncke and David Lebrun and Dirk Steinberg and Robert Raszuk},
    title =     {{IPv6 Segment Routing Header (SRH)}},
    pagetotal = 35,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Segment Routing (SR) allows a node to steer a packet through a controlled set of instructions, called segments, by prepending an 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. Segment Routing 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.},
}