[mpls] Alvaro Retana's No Objection on draft-ietf-mpls-spring-lsp-ping-11: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Wed, 11 October 2017 15:52 UTC

Return-Path: <aretana.ietf@gmail.com>
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 E53F2120720; Wed, 11 Oct 2017 08:52:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alvaro Retana <aretana.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mpls-spring-lsp-ping@ietf.org, mpls-chairs@ietf.org, loa@pi.nu, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150773714593.24751.10157467245954429857.idtracker@ietfa.amsl.com>
Date: Wed, 11 Oct 2017 08:52:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/6yh04ly_Cm_Y1qSx-PTZgMErITs>
Subject: [mpls] Alvaro Retana's No Objection on draft-ietf-mpls-spring-lsp-ping-11: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Oct 2017 15:52:26 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-mpls-spring-lsp-ping-11: No Objection

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:


(1) I’m surprised that there’s not even a passing reference to
draft-ietf-spring-oam-usecase, given that it points to this draft in several
places, among other things as “adding functionality to the use cases described
by this document”.  I'm not advocating for a web of references, just surprised.

(2) The definition of a field with the name “Protocol” in Section 5. (Segment
ID sub-TLV) got me a little confused when I went looking for a registry and
found the values corresponding to the Downstream Detailed Mapping TLV (Section
6).  The name is ok, but I was wondering:  Can you reuse the existing registry
for the values used on the Segment ID sub-TLV?  If so, then the values for
OSPF/ISIS would change.  If not, then please have IANA set one up.

(3) What happens if there’s any error (invalid length, unknown protocol, etc.)
in the sub-TLVs defined in Section 5?  I’m assuming that the action is specific
to the TLV that contains them, or that there is something already specified in
rfc8029 — please include a pointer, or specifics if needed.  I see that Section
7.4. (Segment ID Check) says that other values (for Protocol) “MUST be treated
as Protocol value of 0” — that’s ok for now, but when/if other values are used
this document would have to be Updated.  It may be better to say “any other
unassigned value” (or maybe unrecognized, or something along those lines).

(4) I would really like to see a registry definition for Adj. Type (in 5.3).