IETF Logo Mail Archive

Re: [auth48] [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> for your review

Dino Farinacci <farinacci@gmail.com> Fri, 16 September 2022 21:17 UTC

Return-Path: <farinacci@gmail.com>
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 6080FC1522C0; Fri, 16 Sep 2022 14:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 MvBJDSuzO1Up; Fri, 16 Sep 2022 14:17:45 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 1B731C14CE41; Fri, 16 Sep 2022 14:17:45 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id t3so22580583ply.2; Fri, 16 Sep 2022 14:17:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date; bh=Zkyua+6iJ90+k0oDbXSmSpMraonu8plhxe7yEqqO2cs=; b=q3945DnwRQrbFT2zk8s6izRCR5CGOQAWlJ439L5J0FkN1ZRcFlv45kXH5BTYLDsEtt 7WWd2osxZg3NcR6Cg8WBbrfVHYFpNOJb+5QnEXAFugjruG12f9Hu8FB58e/nXm8OKJt1 BflmH1XIpaKG/KFYGTurCkFoWYRQp88DP6KY0bHdjMqhzC7/6UGFdd8BR7tavn22cGr9 S5v5HmFEov0ZN9IC5PJkta3AtR94AdN/hRbv76yw3wSIrbHICvpsaEGHgsfjLkg4k+Fe uH8RC9cYW/mdbe+JuSxkHRJ4FksJ3diPzX6v7Ii1hZPUY8f7NDIqxn9BX/xAPcbnFByn d0Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=Zkyua+6iJ90+k0oDbXSmSpMraonu8plhxe7yEqqO2cs=; b=GLKnyEsWuIgmG3oJ79cGmf2Bb8Zqm5Kze3YxleyTOAw2kvjoneUu43XUSDbpaHiluj 92K886akRB577rrcdumLfDoy6x7ucdxiUOAw56/e+Iv3x1a4AC2YhH/RFF4ON77+Fc+C Lvftub4h/E2H5kF2Ap78ahmCH3o274ve6Qh9BYUk4F3tsPfVbqbGAr5oSgbE0OeOgeJC oNGT3iXvLV0FnzFQIu2JQPyQAsszdSek6wdOBiEvL88J2ujVaWijLcd89FHqdhL+CYPH t11NMtVpkGEUsobJNdnhWVAmd6EM6qPyTF0UFwrc+ul69squYybU1xQCFvKIr97p5lg+ GOFQ==
X-Gm-Message-State: ACrzQf0t/PWaRqIwku2IIBaQaLF+7xF4nPBTzZus59Qgi7T7n3uuLeVk HXRrAtMs+RxuhgHqyoIeKK21+FtXMCQ=
X-Google-Smtp-Source: AMsMyM4NqV1mMjaUdZnyq7vHxP9mwauM/0VtIvDnLx5VCUPCDQeD5IKrVZvJazEl6mBx1xm5GcIZsg==
X-Received: by 2002:a17:902:c40b:b0:178:e34:efa9 with SMTP id k11-20020a170902c40b00b001780e34efa9mr1700843plk.10.1663363064113; Fri, 16 Sep 2022 14:17:44 -0700 (PDT)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id t4-20020a17090340c400b00172973d3cd9sm15010139pld.55.2022.09.16.14.17.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Sep 2022 14:17:43 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <20220916211431.72DE1AB20F@rfcpa.amsl.com>
Date: Fri, 16 Sep 2022 14:17:42 -0700
Cc: "Alberto Rodriguez-Natal (natal)" <natal@cisco.com>, Vina Ermagan <ermagan@gmail.com>, asmirnov@cisco.com, Vrushali Ashtaputre <vrushali@cisco.com>, lisp-ads@ietf.org, lisp-chairs@ietf.org, Luigi Iannone <ggx@gigix.net>, auth48archive@rfc-editor.org, Dino Farinacci <farinacci@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE390572-328C-46C5-8BEF-DBCEB1731C0E@gmail.com>
References: <20220916211431.72DE1AB20F@rfcpa.amsl.com>
To: RFC Editor <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/WHA4b32usPuBOSJkUUBUWGReomo>
Subject: Re: [auth48] [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> 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: Fri, 16 Sep 2022 21:17:47 -0000

> Authors,
> 
> While reviewing this document during AUTH48, please resolve (as necessary) the following ques
> tions, which are also in the XML file.

Thanks for the review. Here are my responses.

> 1) <!--[rfced] FYI, we updated the short title as follows, which appears in 
> the running header of the PDF file. Please review and let us know if updates
> updates are needed.
> 
> Original:
> LISP-Vendor-LCAF
> 
> Current:
> Vendor-Specific LCAF
> -->

Your text looks good.

> 2) <!--[rfced] FYI, regarding the IANA-registered name "Vendor Specific", 
> within this document, we have updated to use the phrase with a hyphen
> when needed in context, even though it doesn't exactly match the name.
> For example, see the title of the RFC and "the Vendor-Specific LCAF"
> (15 instances total). Please let us know if you prefer otherwise.
> -->

That is fine.

> 3) <!-- [rfced] Please review the "Inclusive Language" portion of the online 
> Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> 
> and let us know if any changes are needed. Note that our script did not flag
> any words in particular, but this should still be reviewed as a best practice.
> -->

Yes, please use inclusive language.

> Thank you.
> 
> RFC Editor/ap/ar

Thank you!

Dino

v2.23.0 | Report a Bug | By Email