%% You should probably cite draft-ietf-idr-bgp-prefix-sid instead of this I-D.
@techreport{keyupate-idr-bgp-prefix-sid-00,
    number =    {draft-keyupate-idr-bgp-prefix-sid-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-keyupate-idr-bgp-prefix-sid/00/},
    author =    {Keyur Patel and Saikat Ray and Stefano Previdi and Clarence Filsfils},
    title =     {{Segment Routing Prefix SID extensions for BGP}},
    pagetotal = 9,
    year =      2014,
    month =     oct,
    day =       25,
    abstract =  {Segment Routing (SR) architecture allows a node to steer a packet flow through any topological path and service chain by leveraging source routing. The ingress node prepends a SR header to a packet containing a set of "segments". Each segment represents a topological or a service-based instruction. Per-flow state is maintained only at the ingress node of the SR domain. The Segment Routing architecture can be implemented using MPLS with no changes to the forwarding plane. It requires minor extensions to the existing routing protocols. This document describes the BGP extension for announcing BGP Prefix Segment Identifier (BGP Prefix SID) information.},
}