Egress Validation in Label Switched Path Ping and Traceroute Mechanisms
draft-ietf-mpls-egress-tlv-for-nil-fec-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mpls-egress-tlv-for-nil-fec@ietf.org, james.n.guichard@futurewei.com, mpls-chairs@ietf.org, mpls@ietf.org, rfc-editor@rfc-editor.org, tsaad.net@gmail.com
Subject: Protocol Action: 'Egress Validation in Label Switched Path Ping and Traceroute Mechanisms' to Proposed Standard (draft-ietf-mpls-egress-tlv-for-nil-fec-15.txt)

The IESG has approved the following document:
- 'Egress Validation in Label Switched Path Ping and Traceroute
   Mechanisms'
  (draft-ietf-mpls-egress-tlv-for-nil-fec-15.txt) as Proposed Standard

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-egress-tlv-for-nil-fec/

Ballot Text

Technical Summary

   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.

Working Group Summary

   Working group had broad agreement to move the document forward to publication.

Document Quality

   Implementation status is provided in section 8 of the document. 

Personnel

   The Document Shepherd for this document is Tarek Saad. The Responsible
   Area Director is Jim Guichard.

RFC Editor Note