Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)
draft-ietf-bess-evpn-lsp-ping-11

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: Matthew Bocci <matthew.bocci@nokia.com>, The IESG <iesg@ietf.org>, andrew-ietf@liquid.tech, bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-evpn-lsp-ping@ietf.org, matthew.bocci@nokia.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'LSP-Ping Mechanisms for EVPN and PBB-EVPN' to Proposed Standard (draft-ietf-bess-evpn-lsp-ping-11.txt)

The IESG has approved the following document:
- 'LSP-Ping Mechanisms for EVPN and PBB-EVPN'
  (draft-ietf-bess-evpn-lsp-ping-11.txt) as Proposed Standard

This document is the product of the BGP Enabled ServiceS Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-lsp-ping/

Ballot Text

Technical Summary

     LSP Ping is a widely deployed Operation, Administration, and
   Maintenance mechanism in MPLS networks.  This document describes
   mechanisms for detecting data plane failures using LSP Ping in MPLS
   based EVPN and PBB-EVPN networks.


Working Group Summary

  Consensus seemed strong and the authors were responsive and addressed the comments and concerns raised.

Document Quality

   While I did not find any concrete statements about current implementations of the draft, the support from the working group and the authors indicate strong support.
  The document is well written and I found it easy to read.  I'd also note that the authors were very responsive to the various directorate reviews and all comments
  received from those reviews seem to have been adequately addressed.

Personnel

   Document Shepherd: Matthew Bocci
   Responsible AD: Andrew Alston

IANA Note

  There are IANA actions as follows:
     - Four new sub-TLV types for the target FEC stack TLV.
     - Two new return codes for the echo reply.
  
  The details of this are correctly described in sections 8.1 and 8.2 of the document.

RFC Editor Note