%% You should probably cite draft-ietf-pce-segment-routing instead of this I-D.
@techreport{sivabalan-pce-segment-routing-00,
    number =    {draft-sivabalan-pce-segment-routing-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-sivabalan-pce-segment-routing/00/},
    author =    {Siva Sivabalan and Clarence Filsfils and Jan Medved and Edward Crabbe and Robert Raszuk},
    title =     {{PCE-Initiated Traffic Engineering Path Setup in Segment Routed Networks}},
    pagetotal = 16,
    year =      2013,
    month =     jun,
    day =       20,
    abstract =  {Segment Routing (SR) enables any head-end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE). It depends only on "segments" that are advertised by Link- State Interior Gateway Protocols (IGPs). A Segment Routed Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a stateful Path Computation Element (PCE). This document specifies extensions to the Path Computation Element Protocol (PCEP) that allow a stateful PCE to signal and instantiate Traffic Engineering paths in SR networks.},
}