[lisp] Martin Duke's Discuss on draft-ietf-lisp-rfc6833bis-27: (with DISCUSS and COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Mon, 06 July 2020 22:51 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 DE1663A0BCF; Mon, 6 Jul 2020 15:51:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-lisp-rfc6833bis@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org, Luigi Iannone <ggx@gigix.net>, ggx@gigix.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <159407591285.9648.16019424277537020150@ietfa.amsl.com>
Date: Mon, 06 Jul 2020 15:51:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/3Nx_Ba8__-tOdzWceo-m0h-COnw>
Subject: [lisp] Martin Duke's Discuss on draft-ietf-lisp-rfc6833bis-27: (with DISCUSS and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 06 Jul 2020 22:51:53 -0000

Martin Duke has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-27: Discuss

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-lisp-rfc6833bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Two issues rise to DISCUSS level, IMO:

Sec 5.7. Is the intent that the Map-Notifies are only retransmitted if they are
unsolicited? If not, repeated Map-Registers could result in a storm of
Map-Notifies.

Sec 7.1. I very well may have missed something, but it doesn't look like the
Map-Request is authenticated. So how can the ETR safely update its Map Cache
based on the information in the Map-Reply?


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

Sec. 5. Please clarify that the 576B and 1280B limits include the entire IP packet.

Sec 5.4. Does the "weight" refer to the percentage of packets or bytes?

Sec 5.5. The first sentence should suggest that the Map Reply could return multiple EID prefixes.