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 2446AC159498; Mon, 6 Jun 2022 14:17:53 -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_DNSWL_BLOCKED=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 Lni2pRomsC9O; Mon, 6 Jun 2022 14:17:52 -0700 (PDT)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 B8EBFC159497; Mon, 6 Jun 2022 14:17:52 -0700 (PDT)
Received: by mail-wm1-x32c.google.com with SMTP id e5so1458775wma.0; Mon, 06 Jun 2022 14:17:52 -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=S1QVA5lwCtGmfzSl+PDe/ipmTh0kXP291E0c61PV0PU=; b=HLh/4d6fABU0gLbsC3fq7rjxbeHdanf6w1BZ9fLAIH7flpE4CHWx+99oOrMjQ2A+aG D0E6BvSSlQQNlVkOyElgWvX0wgPmd7K2mn1dnKCZnFa0OED201niJ021+vlPtWEkW2nv Cx5JvTY77BTeqol1MfQBNeAkfhI2uhoC9OK1HjYZ3sz8YuTJVoILIFnXlW2DLxOhwaHc qbRB1u87swbGyqvEUR+Bsk65TjKCPJMQ6q0AFetuFuSKJch0hcbSPXAwqf4w2nwkQPat wd91qs3w7nJbZX6SFr06VM6cVz8oKKqiBbbbW5/0oj0lyPJjaxPtXOw6wDy4foiyhXSC 67AA==
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=S1QVA5lwCtGmfzSl+PDe/ipmTh0kXP291E0c61PV0PU=; b=DOTfuUrT2YEjbnywL8mbuVvRw/qzsR1bTG+XbAsqVc5hXVyi2eMcTQLi3fEbj6vXkB l9qJL/tXgvRLQWqKi7U+qKea8taP1DJBPkD50U4oG2K0XaErlJ4FIV69+2GfNn801qir YUWflK5QTHSBkmzI5v0G6JWKy1jzFGefxOgKRydROCwzDhj784TEePcjAohpRWiReP1M 9B4GqQZzmcp/VTiCP9eNZ/XKw7uhjY31b6/lK4r1DYzaP4oM/Ox/L0hPVGjSbfKZ+k96 Lr0w9Moy5AHa9xylNdnatn5TJn4k1cYn+uu7MNDvb7M9GhItBFXRQeFhHdJ3U5XsTMa6 7PFA==
X-Gm-Message-State: AOAM530LNu1C41W1AiutJDCuBtsBYlcquO/ZHQK/Tx8zCdNaolREKKwp NPHVWuTBbImMezdxfwy4cPYOGx17GYpJmO1Z5Vbh6kOEi2g=
X-Google-Smtp-Source: ABdhPJxJO4t4/Tm3OCrO6M8Wtk9ZPk7GPjK0h8D9SViAFMouLg6Qei8c51R3a1DJ4Tae2lQwSaWFYZHFX3FJr+EnTds=
X-Received: by 2002:a05:600c:2054:b0:39c:3f73:3552 with SMTP id p20-20020a05600c205400b0039c3f733552mr19519500wmg.15.1654550270798; Mon, 06 Jun 2022 14:17:50 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 6 Jun 2022 14:17:50 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <FDF564CD-E0C6-4A8D-A715-46278EC81992@getnexar.com>
References: <CAMMESsy+GKwKaR1Zf2uOF9ggnHQoRkA_tv-eRQQiKsvp_FJHWA@mail.gmail.com> <CAMMESswFg8=QD1LcqMJb-+wTdW-hQ1x0oQQqVifY24P9KgYqNQ@mail.gmail.com> <FDF564CD-E0C6-4A8D-A715-46278EC81992@getnexar.com>
MIME-Version: 1.0
Date: Mon, 06 Jun 2022 14:17:50 -0700
Message-ID: <CAMMESsz+3mjYMiD=CvQRD-anL6=QJ+eqMYw9CeM4taEJqJBLuQ@mail.gmail.com>
To: Sharon Barkai <sharon.barkai@getnexar.com>
Cc: lisp@ietf.org, lisp-chairs@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/Yv85MWs0nELHJrnHOLQaRh8ODnM>
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:53 -0000

On June 5, 2022 at 7:23:03 PM, Sharon Barkai wrote:

Sharon:

Hi!


...
> I am attaching such a narrower problem rephrasing draft.
> Was wondering if this direction is acceptable in your view.

The updated Introduction is clearer, but maybe because I know what you
want to do -- the first couple of paragraphs still contain a lot of
words that give the impression that the document is about satisfying
the geolocation and tracking threats.  In fact, the forth paragraph
starts by saying that the "issues are resolved by dataflow
virtualization, or communication indirection...LISP overlay
network-virtualization can offer such a solution".  This is a bold
claim that will need to be substantiated.  It would serve the document
if an analysis in line with rfc6973 of how LISP can address the
specific threats is included.

The (short) Privacy Considerations section in rfc6833bis includes some
information that may be useful to build from.  OTOH, rfc7835 leaves
out any privacy considerations by arguing that "privacy definitions
may vary for different scenarios".  Well, you have one such scenario.


It is important that it is made clear which aspects of the system are
out of scope for LISP and are provided as an example.  To be clear, I
want to explicitly see the words "out of scope" prominently mentioned.

The Notes help a little, but there is still a lot more detail than is
necessary for a LISP document.  For example, the AAA flow diagram,
application packet formats, etc.


In summary, I think the introduction helps, but there is still a lot
of work to be done.

BTW, to facilitate my review of the changes, I expect an inline reply
to the comments.


Thanks!

Alvaro.