[lisp] Alvaro Retana's No Objection on draft-ietf-lisp-gpe-06: (with COMMENT)
Alvaro Retana <aretana.ietf@gmail.com> Tue, 25 September 2018 18:14 UTC
Return-Path: <aretana.ietf@gmail.com>
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 541721286E3; Tue, 25 Sep 2018 11:14:21 -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-lisp-gpe@ietf.org, Luigi Iannone <ggx@gigix.net>, lisp-chairs@ietf.org, lisp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.84.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153789926133.5101.18151906676525764346.idtracker@ietfa.amsl.com>
Date: Tue, 25 Sep 2018 11:14:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/xUdEfOExD8pB-HIl9wTN59SABFA>
Subject: [lisp] Alvaro Retana's No Objection on draft-ietf-lisp-gpe-06: (with 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: Tue, 25 Sep 2018 18:14:21 -0000
Alvaro Retana has entered the following ballot position for draft-ietf-lisp-gpe-06: 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: https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I have some non-blocking comments (and nits): (1) §1: "LISP-GPE MAY also be used to extend the LISP Data-Plane header..." I think that MAY is out of place because there's nothing normative about the statement. (2) §3: "If the P-bit is clear (0) the LISP header conforms to the definition in [I-D.ietf-lisp-rfc6830bis]." I find this statement a little confusing because even with the bit set, the header still conforms to rfc6830bis, except for the Nonce/Map-Version field. IOW, it sounds as if the bit makes the header non-conforming. (3) §3: For clarity, it would be nice to add a figure showing the header with the P and V bits set. (4) §3.1: "...the specification of a new encapsulated payload MUST contain an analysis of how LISP-GPE SHOULD deal with..." s/SHOULD/should In this case the "SHOULD" is not normative. (5) For IP packets, two encapsulation mechanisms exist, the base one defined in rfc6830bis and the generic one defined in this document. When encapsulating towards a GPE-capable router, which mechanisms should be used? Should one have preference over the other? I'm thinking it probably doesn't matter (since the receiving router can understand both) -- I'm trying to figure out whether there are operational considerations or guidance that are worth mentioning.
- [lisp] Alvaro Retana's No Objection on draft-ietf… Alvaro Retana
- Re: [lisp] Alvaro Retana's No Objection on draft-… Fabio Maino