%% You should probably cite draft-zjns-mpls-lsp-ping-relay-reply instead of this I-D.
@techreport{zj-mpls-lsp-ping-reply-relay-00,
    number =    {draft-zj-mpls-lsp-ping-reply-relay-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-zj-mpls-lsp-ping-reply-relay/00/},
    author =    {Lizhong Jin and Zhi Zheng},
    title =     {{LSP Ping extensions for echo reply relay}},
    pagetotal = 8,
    year =      2011,
    month =     oct,
    day =       23,
    abstract =  {{[}RFC4379{]} describes the LSP Ping mechanism to detect data plane failures. In some deployment scenario for the LSP traceroute, a replying LSR may not have the available route to the initiator, and the echo reply message sent to the initiator would be discarded. Thus, the basic idea of traceroute procedure to localize fault could not be achieved. This document describes extensions to LSP Ping mechanism to enable the replying LSR to have the capability to relay the echo reply by a set of routable intermediate nodes to the initiator.},
}