[lisp] Éric Vyncke's No Objection on draft-ietf-lisp-name-encoding-09: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 29 July 2024 15:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172226645873.1736260.917722532312546388@dt-datatracker-659f84ff76-9wqgv>
Date: Mon, 29 Jul 2024 08:20:58 -0700
Message-ID-Hash: QFEQF3IWM2DO6HR3BDSNB3UQAFLQ7CXA
CC: draft-ietf-lisp-name-encoding@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org, tim@qacafe.com
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [lisp] Éric Vyncke's No Objection on draft-ietf-lisp-name-encoding-09: (with COMMENT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/Rlm2KMreyqmJQ2hZNhj3jd_ps_w>

Éric Vyncke has entered the following ballot position for
draft-ietf-lisp-name-encoding-09: 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/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lisp-name-encoding/

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

# Éric Vyncke, INT AD, comments for draft-ietf-lisp-name-encoding-09

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education).

Special thanks to Alberto Rodriguez-Natal for the shepherd's detailed write-up
including the WG consensus _and_ the justification of the intended status.

Other thanks to Tim Winters, the Internet directorate reviewer (at my request),
please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-lisp-name-encoding-09-intdir-telechat-winters-2024-07-25/

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## Abstract

Normally, it is expected that abstracts are short, but this one is probably a
little too short.

## Section 2

Is there an inversion in `An address is family currently defined` ?

## Section 3

Unsure whether using ASCII rather than UTF-8 is wise.

I am not familiar enough but it seems that the length field is sometimes
expressed in bit units or in octect units. Adding some clarifications would be
welcome.

`then any length field is the length` is really unclear with the use of "any"
in the sentence.

## Section 4

Is the match case sensitive ? Nothing is said.

## Section 5

Please avoid using a commercial USA name "GPS" in `GPS coordinate mappings`
rather use the "GNSS" term (that applies to Galileo, GPS, ...) or even remove
"GPS" entirely.

## Section 7

Nothing is specified when the NULL character is not present.

[lisp] Éric Vyncke's No Objection on draft-ietf-l… Éric Vyncke via Datatracker