<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.rathi-mpls-egress-tlv-for-nil-fec" target="https://datatracker.ietf.org/doc/html/draft-rathi-mpls-egress-tlv-for-nil-fec-06">
   <front>
      <title>Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute Mechanisms</title>
      <author initials="D. N." surname="Rathi" fullname="Deepti N. Rathi">
         <organization>Juniper Networks Inc.</organization>
      </author>
      <author initials="K." surname="Arora" fullname="Kapil Arora">
         <organization>Juniper Networks Inc.</organization>
      </author>
      <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
         <organization>Juniper Networks Inc.</organization>
      </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="N. K." surname="Nainar" fullname="Nagendra Kumar Nainar">
         <organization>Cisco Systems</organization>
      </author>
      <date month="August" day="19" year="2021" />
      <abstract>
	 <t>   MPLS ping and traceroute mechanism as described in RFC 8029 and
   related extensions for SR as defined in RFC 8287 is very useful to
   precisely validate the control plane and data plane synchronization.
   There is a possibility that all intermediate or transit nodes may not
   have been upgraded to support these validation procedures.  A simple
   mpls ping and traceroute mechanism comprises of ability to traverse
   any path without having to validate the control plane state.  RFC
   8029 supports this mechanism with Nil FEC.  The procedures described
   in RFC 8029 are mostly applicable when the Nil FEC is used as
   intermediate FEC in the label stack.  When all labels in label stack
   are represented using single Nil FEC, it poses some challenges.

   This document introduces new TLV as additional extension to exisiting
   Nil FEC and describes mpls ping and traceroute procedures using Nil
   FEC with this additional extensions to overcome these challenges.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-rathi-mpls-egress-tlv-for-nil-fec-06" />
   
</reference>
