The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document: - 'Egress Validation in Label
Switched Path Ping and Traceroute
   Mechanisms'
  <draft-ietf-mpls-egress-tlv-for-nil-fec-13.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2024-05-17. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mpls-egress-tlv-for-nil-fec/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/5656/






_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to