%% You should probably cite rfc9086 instead of this I-D.
@techreport{ietf-idr-bgpls-segment-routing-epe-18,
    number =    {draft-ietf-idr-bgpls-segment-routing-epe-18},
    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-idr-bgpls-segment-routing-epe/18/},
    author =    {Stefano Previdi and Ketan Talaulikar and Clarence Filsfils and Keyur Patel and Saikat Ray and Jie Dong},
    title =     {{BGP-LS extensions for Segment Routing BGP Egress Peer Engineering}},
    pagetotal = 18,
    year =      2019,
    month =     mar,
    day =       24,
    abstract =  {Segment Routing (SR) leverages source routing. 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 segments allow steering a flow through any topological path and service chain while maintaining per-flow state only at the ingress node of the SR domain. This document describes an extension to BGP Link State (BGP-LS) for advertisement of BGP Peering Segments along with their BGP peering node information so that efficient BGP Egress Peer Engineering (EPE) policies and strategies can be computed based on Segment Routing.},
}