%% You should probably cite draft-ietf-mpls-egress-tlv-for-nil-fec instead of this I-D.
@techreport{rathi-mpls-egress-tlv-for-nil-fec-01,
    number =    {draft-rathi-mpls-egress-tlv-for-nil-fec-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-rathi-mpls-egress-tlv-for-nil-fec/01/},
    author =    {Deepti N. Rathi and Kapil Arora and Shraddha Hegde},
    title =     {{Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute Mechanisms}},
    pagetotal = 8,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Segment routing supports the creation of explicit paths using adjacency- sids, node-sids, and anycast-sids. The SR-TE paths are built by stacking the labels that represent the nodes and links in the explicit path. A very useful Operations And Maintenance (OAM) requirement is to be able to ping and trace these paths. A simple mpls ping/traceroute mechanism comprises of ability to traverse the SR-TE path without having to validate the control plane state. This document describes mpls ping and traceroute procedures using Nil FEC with additional extensions.},
}