Re: [auth48] [C336] [AD] RE: AUTH48: RFC-to-be 9299 <draft-ietf-lisp-introduction-15> for your review

Luigi Iannone <ggx@gigix.net> Wed, 14 September 2022 13:18 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48048C1522A9 for <auth48archive@ietfa.amsl.com>; Wed, 14 Sep 2022 06:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20210112.gappssmtp.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 iVWUt3A4OxOb for <auth48archive@ietfa.amsl.com>; Wed, 14 Sep 2022 06:18:17 -0700 (PDT)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 56CB8C1522A6 for <auth48archive@rfc-editor.org>; Wed, 14 Sep 2022 06:18:17 -0700 (PDT)
Received: by mail-wm1-x329.google.com with SMTP id z14-20020a05600c0a0e00b003b486df42a3so6393871wmp.2 for <auth48archive@rfc-editor.org>; Wed, 14 Sep 2022 06:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20210112.gappssmtp.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date; bh=yezal3e36M9n1clU9yzxPBKdi1v0F+wZOKZn/2VMr0c=; b=cq0sf4rTvGLrvEyXHhAzwVjqx2A0Yp5LByl8RPEbyczc0LQNLz5evWvqaCOpsj4h6G 7dok1tFMnU3DUspsF5H9iviCZgOFobfkZshNM69/gXOWInh/04z1uTIc0c94K0ZOscNG ZzzXt6BObutCVB4m0NNCAbMm4uPWjBb06RkTK2RabWMTn0/dmmE5R2JnUAR1fKhjFStE Dtlg3ukDWA8HvY0fvnK+eKhkq2mHfPa2x6A9ekwtZ0nTf5l/mc27kRM999kmbpaA6FcF LbAPejPd6QFzbnQs5vCW91zLjOlQUjx0X3ZQMyYgyH0ND678HSUD1sIiNJich1Huce5l 6Q0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date; bh=yezal3e36M9n1clU9yzxPBKdi1v0F+wZOKZn/2VMr0c=; b=NQaTSWTfpT5CsWJZ40HEbz4HGDMkmy7G1lVux4JbONGAEZrC4CwgHhBWuZF2Aay11p Oj0qVTPVxRKEA83XkyqMIipvek793OXDaDZCykxdIOUHI2AMrFCrhq4ZKlF6UktWFh50 63oDyUDFZrmv7sjwZlvuixh4/oIALhB3X6reFnLWdGD4NDjzbBJrt483I7sIKU9tOp6y 53lYKEelrLZjlul7Yp/svl9rxJMcCKxXNyqIxPt0ZWeu1tmgp1koaXMjIE14CbgkWS4e 0NKgeDx+GZ3ud0W1GKadL1EqsXuF8A2oHYFGjzcMT4yj85/koXRUzHZmJ8blaoBC2UbW 5kqQ==
X-Gm-Message-State: ACgBeo2sJQNXfDrLEnx4fPYzsQcNzvQJGWmoe8IB6dpZ3VMZSroo2+42 vVYyIKYpp5coviUX06BznMg4ow==
X-Google-Smtp-Source: AA6agR7deYmVLODxosty8eSOl5qc3K8xDGrPKciJqKkkoL7DzIDTmjkwukgHgbyvPItY1CyrKNCLKQ==
X-Received: by 2002:a05:600c:22d3:b0:3a8:424d:f386 with SMTP id 19-20020a05600c22d300b003a8424df386mr3095866wmg.57.1663161495298; Wed, 14 Sep 2022 06:18:15 -0700 (PDT)
Received: from smtpclient.apple ([37.170.88.150]) by smtp.gmail.com with ESMTPSA id d7-20020a5d4f87000000b0022ac61ebb14sm2325574wru.22.2022.09.14.06.18.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Sep 2022 06:18:14 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Message-Id: <706BA4B5-7F03-415C-B38C-A2A7F13430DC@gigix.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6DF97496-E953-4DB5-A7AD-2CEB8DA9D0C8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Wed, 14 Sep 2022 15:18:12 +0200
In-Reply-To: <CAHS_mjH+ni0oqNjqMVn6Vp+Kri2WxjiQz0FyFJgvXJeUZ0-veA@mail.gmail.com>
Cc: RFC Editor <rfc-editor@rfc-editor.org>, Albert CABELLOS <acabello@ac.upc.edu>, Damien Saucez <damien.saucez@inria.fr>, lisp-ads@ietf.org, lisp-chairs@ietf.org, auth48archive@rfc-editor.org
To: Albert Cabellos <alberto.cabellos@upc.edu>
References: <20220907050157.B644B4C29E@rfcpa.amsl.com> <CAHS_mjH+ni0oqNjqMVn6Vp+Kri2WxjiQz0FyFJgvXJeUZ0-veA@mail.gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/BJ54-jJrsToNdBHkBztaswnmvYU>
Subject: Re: [auth48] [C336] [AD] RE: AUTH48: RFC-to-be 9299 <draft-ietf-lisp-introduction-15> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2022 13:18:22 -0000

Hi,

Thanks Albert.

Just as a very minor suggestions:


> On 14 Sep 2022, at 14:58, Albert Cabellos <alberto.cabellos@upc.edu> wrote:
> 
> 
> 4) <!-- [rfced] There are a couple of places that refer to "at the time of 
> this writing".  Please review and let us know if any updates are desired, as 
> this document was approved in 2015.  
> 
> Section 3.2 Original: 
>    EIDs are IPv4 or IPv6
>    addresses that uniquely identify communication end-hosts and are
>    assigned and configured by the same mechanisms that exist at the time
>    of this writing.
> 
> Section 4.3 Original:
>    At the time of this writing LISP does not specify a mechanism to
>    achieve ETR synchronization.
> -->
> 
> 
> No updates are required. 

This may lead confusion with the publication date.
What is we add: “… time of this writing (Editor’s Note: 2015)…”

What do you think?
> 26) <!-- [rfced] Please review the "Inclusive Language" portion of the online 
> Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>> 
> and let us know if any changes are needed.  For example, please consider 
> whether "natively" or "native" should be updated.
> -->
> 
> 
> 
> I have reviewed the document and I have not identified any instance where a change is required.

May be:

Replace the only occurrence of “natively” with “as-is”

Replace the only occurrence of “native” with “original”

What do you think?

> 
> Thanks for the outstanding review, I am really impressed how the readability and correctness of the document has improved. 
> 

+1

Thanks

L.



> Albert