[mpls] Barry Leiba's Yes on draft-ietf-mpls-lsp-ping-registries-update-07: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Wed, 03 February 2021 16:05 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7E23A0B13; Wed, 3 Feb 2021 08:05:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mpls-lsp-ping-registries-update@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, adrian@olddog.co.uk
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <161236831341.9485.18193185236932633068@ietfa.amsl.com>
Date: Wed, 03 Feb 2021 08:05:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/rtPxmv_IRNJWRZBcYqPdXBmnpn4>
Subject: [mpls] Barry Leiba's Yes on draft-ietf-mpls-lsp-ping-registries-update-07: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2021 16:05:14 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-mpls-lsp-ping-registries-update-07: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-registries-update/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

At first I was puzzled by the move from Specification Required to RFC Required,
until I looked in RFC 8209 at this:

   Values from "Specification Required" ranges MUST be registered with
   IANA.  The request MUST be made via an RFC that describes the format
   and procedures for using the code point; the actual assignment is
   made during the IANA actions for the RFC.

In other words, it's really always been RFC Required, but specified in an odd
way and with a designated expert looking at it.

So, yes, this is a useful cleanup and clarification, and thanks for doing this.
 And, as you have in the Acknowledgments, thanks to Michelle for working with
you to make sure this came out right.