[lisp] Paul Wouters' No Objection on draft-ietf-lisp-6834bis-11: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Tue, 31 May 2022 20:03 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 3D75BC14F73F; Tue, 31 May 2022 13:03:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters 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: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <165402739524.5813.12474772194728200219@ietfa.amsl.com>
Date: Tue, 31 May 2022 13:03:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/cz7dGh2yAFEof4ZWf63Y3b591YM>
Subject: [lisp] Paul Wouters' 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 20:03:15 -0000

Paul Wouters 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:
----------------------------------------------------------------------

#1  map-version rollover is defined (to skip the 0 version) but I also see:

The packet arrives with a Dest Map-Version number greater (i.e.,
       newer) than the one stored in the EID-to-RLOC Database.  Since
       the ETR is authoritative on the mapping, meaning that the Map-
       Version number of its mapping is the correct one

This would imply rollover to a smaller number is not expected to occur ?

#2 MUST NOT or SHOULD ?

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

This sentence seems to contradict itself. I would turn the SHOULD into a MUST