@techreport{farrel-mpls-lsp-ping-tlvs-01,
    number =    {draft-farrel-mpls-lsp-ping-tlvs-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-farrel-mpls-lsp-ping-tlvs/01/},
    author =    {Adrian Farrel and George Swallow},
    title =     {{Future-Proof TLV Codepoint Space for LSP Ping}},
    pagetotal = 10,
    year =      2007,
    month =     nov,
    day =       17,
    abstract =  {Techniques for detecting Multi-Protocol Label Switched (MPLS) data plane failures are described in RFC 4379 and include the definition of a control protocol for testing and verifying Label Switched Path (LSP) connectivity that is known as LSP Ping. The protocol consists of a set of messages each of which contains data encoded as TLVs. The LSP Ping protocol is being extended for several related uses. Each extension gives rise to the definition of new TLVs to be carried on the existing protocol messages. The LSP Ping specification makes it mandatory that all TLVs are understood by each participating Label Switching Router (LSR) that receives an LSP Ping message. This makes future extensibility hard without upgrading all LSRs in the network. This document defines ranges in the TLV codepoint space so that TLVs may be associated with different processing rules within an LSR if the TLV is unknown. This will make extensibility more simple.},
}