%% You should probably cite draft-nainar-mpls-spring-lsp-ping-sr-generic-sid-06 instead of this revision.
@techreport{nainar-mpls-spring-lsp-ping-sr-generic-sid-05,
    number =    {draft-nainar-mpls-spring-lsp-ping-sr-generic-sid-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-nainar-mpls-spring-lsp-ping-sr-generic-sid/05/},
    author =    {Nagendra Kumar Nainar and Carlos Pignataro and Zafar Ali and Clarence Filsfils and Tarek Saad},
    title =     {{Segment Routing Generic TLV for MPLS Label Switched Path (LSP) Ping/ Traceroute}},
    pagetotal = 10,
    year =      2021,
    month =     may,
    day =       18,
    abstract =  {RFC8402 introduces Segment Routing architecture that leverages source routing and tunneling paradigms and can be directly applied to the Multi Protocol Label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called segments, by prepending the packet with Segment Routing header. SR architecture defines different types of segments with different forwarding semantics associated. SR can be applied to the MPLS directly and to IPv6 dataplane using a new routing header. 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. Various SIDs are proposed as part of SR architecture with different associated instructions that raises a need to come up with new Target FEC Stack Sub-TLV for each such SIDs. This document defines a new Target FEC Stack Sub-TLV that is used to validate the instruction associated with any SID.},
}