%% You should probably cite draft-ietf-mpls-egress-tlv-for-nil-fec-13 instead of this revision.
@techreport{ietf-mpls-egress-tlv-for-nil-fec-12,
    number =    {draft-ietf-mpls-egress-tlv-for-nil-fec-12},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mpls-egress-tlv-for-nil-fec/12/},
    author =    {Deepti N. Rathi and Shraddha Hegde and Kapil Arora and Zafar Ali and Nagendra Kumar Nainar},
    title =     {{Egress Validation in Label Switched Path Ping and Traceroute Mechanisms}},
    pagetotal = 12,
    year =      2024,
    month =     mar,
    day =       1,
    abstract =  {The MPLS ping and traceroute mechanism as described in RFC 8029 and related extensions for Segment Routing(SR) as defined in RFC 8287 is very useful to validate the control plane and data plane synchronization. In some environments, only some intermediate or transit nodes may have been upgraded to support these validation procedures. A simple MPLS ping and traceroute mechanism allows traversing any path without validating the control plane state. RFC 8029 supports this mechanism with Nil Forwarding Equivalence Class (FEC). The procedures described in RFC 8029 mostly apply when the Nil FEC is used as an intermediate FEC in the label stack. When all labels in the label stack are represented using Nil FEC, it poses some challenges. This document introduces a new Type-Length-Value (TLV) as an extension to exisiting Nil FEC. It describes MPLS ping and traceroute procedures using Nil FEC with this extension to overcome these challenges.},
}