[lisp] Éric Vyncke's No Objection on draft-ietf-lisp-6834bis-11: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 31 May 2022 07:54 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: lisp@ietf.org
Delivered-To: lisp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF146C14F724; Tue, 31 May 2022 00:54:26 -0700 (PDT)
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>
Cc: draft-ietf-lisp-6834bis@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org, Padma Pillay-Esnault <padma.ietf@gmail.com>, padma.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.3.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <165398366690.4808.1838513220300138370@ietfa.amsl.com>
Date: Tue, 31 May 2022 00:54:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/N9graXc9rzbDBXkd-3NgBGnIY88>
Subject: [lisp] Éric Vyncke's No Objection on draft-ietf-lisp-6834bis-11: (with COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.34
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2022 07:54:27 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-lisp-6834bis-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/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-6834bis/



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

# Éric Vyncke, INT AD, review of draft-ietf-lisp-6834bis-11

Thank you for the work put into this document.

Please find below some blocking DISCUSS points (easy to address), some
non-blocking COMMENT points (but replies would be appreciated even if only for
my own education), and some nits.

Special thanks to Padma Pillay-Esnault for the shepherd's write-up including
the WG consensus and the intended status.

I hope that this helps to improve the document,

Regards,

-éric

## DISCUSS

As noted in https://www.ietf.org/blog/handling-iesg-ballot-positions/, a
DISCUSS ballot is a request to have a discussion on the following topics:

### Section 2.2

## COMMENTS

### Section 6

Just wondering why having an algorithm defined for 'N' while the versions are
always on 12 bits.

### Section 8

```
Map-Versioning MUST NOT be used over the public Internet and SHOULD
   only be used in trusted and closed deployments.
```

An explanation of why and how would be welcome. Feel free to ignore this
comment though as this is the usual recommendation for any tunneling mechanism
w/o authentication/confidentiality.

## NITS

### Section 6

s/MUST consist in an increment by one the older/MUST consist in an increment by
one of the older/ ? Moreover, 'increment' is usually understood as 'add 1' so
no need to add 'by one' in the sentence

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues.

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments