%% You should probably cite draft-iqbal-spring-mpls-ping-algo-02 instead of this revision.
@techreport{iqbal-spring-mpls-ping-algo-00,
    number =    {draft-iqbal-spring-mpls-ping-algo-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-iqbal-spring-mpls-ping-algo/00/},
    author =    {faiqbal@cisco.com and Nagendra Kumar Nainar and Zafar Ali and Carlos Pignataro},
    title =     {{Supporting Flexible Algorithm Prefix SIDs in LSP Ping/Traceroute}},
    pagetotal = 7,
    year =      2018,
    month =     jun,
    day =       28,
    abstract =  {RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier (SIDs) with an MPLS data plane. {[}I-D.ietf-lsr-flex-algo{]} proposes a mechanism to allow IGPs to compute constraint based path over network and use Segment Routing Prefix-SIDs to steer packets along the constraint-based paths. All Prefix-SIDs associated with the Flexible Algorithm are assigned to the same IPv4/IPv6 Prefix. Any Segment Routing network that uses Flexible Algorithm based path computation needs additional details to be carried in the FEC Stack sub-TLV for FEC validaiton. This document updates {[}RFC8287{]} by modifying IPv4 and IPv6 IGP-Prefix Segment ID FEC sub-TLVs to also include algorithm identification.},
}