IETF Logo Mail Archive

Re: [lisp] AD Review of draft-ietf-lisp-nexagon-19

Alvaro Retana <aretana.ietf@gmail.com> Mon, 06 June 2022 21:17 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A991DC159498; Mon, 6 Jun 2022 14:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LW87sZZGIYgg; Mon, 6 Jun 2022 14:17:27 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 393D8C159497; Mon, 6 Jun 2022 14:17:27 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id p10so21456823wrg.12; Mon, 06 Jun 2022 14:17:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=hvylMQu6gNcV3zNLiOYWpgzWA/SyXf47hj+06o4EIus=; b=E0dNVfT9pT5Jg+eS/WZ5JX0YmzotIk6FctOYWa+PA+V2OBQpPc21/zy8KcmcTqo63j PwDLuqu/axvM5pk+Q6g0Xoz3rJ6rBQUpCA/wcyL2fdu3wy4v8jg09bLWOIqqSfG8zDsB pUC2cM9ODmtRH6EXrdAlOIw51JRo4nG8xQskRUwpGC4wM7Zxomkgvhtx1H/kInPcr2JH h0BRA2V1SzGWo1NZxMBrhx6nW/AFg3IfnMvOXuqWuCuPvF2xOE6V/EqnoeVaQoIHT6ue HuUQhbEWHEvMkTKo3TIp7L+ZdFkLdxBVYhSzSlXD6VsujYHHsW4NJPhZX+g5quc+IfHr 7P+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=hvylMQu6gNcV3zNLiOYWpgzWA/SyXf47hj+06o4EIus=; b=VEiQTEDHYCVo2go0uG6yj3PjirBt3VO4z7qWJ/OxsyqLDs9adSmYAcD/nrrfHFvdQ5 +CLXhzFALYNdloS+p1DwhfZ0ZEj6LuIlNoMOVHYD9bpegiI3AxXe2Es0Livs5jN6XEMI MfMr/cXxrE5i0UYiYCvMNncRFBwUnKew62HXeJ/f2aBKQQ6O91lZLIfeuFKnkxqKcZJA T/4pnt/W6w8OsP59vaLHtZfjUME0uhLEDnDPfFsE0qaBhqkrPZqb+46OExAf9EI6jmwq 8hIa+GjcIWXKsIheO8LLRAp5f27+KF7LrA/ybfU0GjPpLYaXYh7RVYECsaazDodHdvIR w/2w==
X-Gm-Message-State: AOAM5322xKWTWvchIr8bd9oCOlqSQjcAgTgTYhDZcIvTiEbn2Fv5rkPG 9WJL+UtPhvPp4OF0tcmH0RSthi7orvmv0uhK3t6YUvTGytw=
X-Google-Smtp-Source: ABdhPJyvhG13TfBpWkUxjd9wOG+Us7mij2yrpyaIWZ/8Jr1EEG4zrL2N0HNAMa5zYzqwgvMH5znD3njRq4bkkkBuUs0=
X-Received: by 2002:adf:fb52:0:b0:216:9eff:342b with SMTP id c18-20020adffb52000000b002169eff342bmr12690156wrs.356.1654550245088; Mon, 06 Jun 2022 14:17:25 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 6 Jun 2022 14:17:24 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <f1accab3-236b-052c-ba64-d03617f8dae5@joelhalpern.com>
References: <CAMMESsy+GKwKaR1Zf2uOF9ggnHQoRkA_tv-eRQQiKsvp_FJHWA@mail.gmail.com> <f1accab3-236b-052c-ba64-d03617f8dae5@joelhalpern.com>
MIME-Version: 1.0
Date: Mon, 06 Jun 2022 14:17:24 -0700
Message-ID: <CAMMESswnHEH17WktdRG5HwK9um0ppQx5keZmubt7nvYfpeiXdA@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: lisp-chairs@ietf.org, lisp@ietf.org, draft-ietf-lisp-nexagon@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/pNFoOsuij7ZB1O8S7B2Nr1kiX0w>
Subject: Re: [lisp] AD Review of draft-ietf-lisp-nexagon-19
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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 Jun 2022 21:17:27 -0000

On June 3, 2022 at 7:18:01 PM, Joel Halpern wrote:


Joel:

Hi!


> It is clear that this document is on the edge of the charter for the
> LISP WG. It does not change LISP, but rather explains how to use LISP
> to achieve a goal. Of course, if it were in some other WG it would
> still need LISP review, so keeping it here makes snse. Particular since
> it is not really about ipwave stuff.

The part of the draft that describes the use of LISP is confusing and
incomplete, but that can be fixed.

However, there are other parts that are not about LISP.  Those parts
are the ones that I don't think belong to this WG: AAA extensions, H3
specifics, application layer packet formats, etc.

I see that Sharon started looking at my review, so let's wait and see
what shape the document takes.


> The other important note is that way back when Sharon first brought this
> work forward, I went to various AD, chairs, and influential participants
> and tried to get a review on the geoloc / geopriv dimensions so that we
> could properly consider them. I could one review, which brought up only
> a few points (which Sharon then clarified in the draft.) It was very
> clear that there was no interest from that community in looking closely
> and engaging on this work.

No interest by the community is not a positive indicator. :-(

Thanks for the extra background.


Alvaro.

v2.23.0 | Report a Bug | By Email