Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for

Rebecca VanRheenen <rvanrheenen@amsl.com> Mon, 03 October 2022 18:15 UTC

Return-Path: <rvanrheenen@amsl.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 C86CFC152560; Mon, 3 Oct 2022 11:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=unavailable autolearn_force=no
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 Eny-5MBWYBID; Mon, 3 Oct 2022 11:15:51 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 15774C152562; Mon, 3 Oct 2022 11:15:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 014D5425C152; Mon, 3 Oct 2022 11:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkW_uWWqAeNT; Mon, 3 Oct 2022 11:15:50 -0700 (PDT)
Received: from [IPv6:2601:641:300:5fb0:b405:4cc3:d68e:4f37] (unknown [IPv6:2601:641:300:5fb0:b405:4cc3:d68e:4f37]) by c8a.amsl.com (Postfix) with ESMTPSA id B6E004243EC3; Mon, 3 Oct 2022 11:15:50 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20220930062310.wd7pnu6ywhw52lmw@benm-laptop>
Date: Mon, 03 Oct 2022 11:15:50 -0700
Cc: RFC Editor <rfc-editor@rfc-editor.org>, "sidrops-ads@ietf.org" <sidrops-ads@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, Warren Kumari <warren@kumari.net>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E877E63-DF5F-41F4-8B18-1D19B173F11B@amsl.com>
References: <20220927053320.A4B3A4C956@rfcpa.amsl.com> <20220927134731.k5ly7e7yi2cnxhvb@benm-laptop> <559B18A8-CAA4-4855-82BF-7CCB183E6F91@amsl.com> <20220928085932.5x6k374wer6ulmyd@benm-laptop> <88C3FBCA-95BF-4568-9F4D-8CBCC55A71EF@amsl.com> <SA1PR09MB81425174252C5FEA97663B0D84569@SA1PR09MB8142.namprd09.prod.outlook.com> <20220930062310.wd7pnu6ywhw52lmw@benm-laptop>
To: Ben Maddison <benm@workonline.africa>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, "yossigi@cs.huji.ac.il" <yossigi@cs.huji.ac.il>, "goldbe@cs.bu.edu" <goldbe@cs.bu.edu>, Job Snijders <job@fastly.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/kCc75Ts80hiu6J5ZC6xmll04fEc>
Subject: Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for
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: Mon, 03 Oct 2022 18:15:54 -0000

Hi Sriram and Ben,

Ben, we have noted your approval on the AUTH48 status page for this document (see https://www.rfc-editor.org/auth48/rfc9319).

We also made the update in the Introduction as suggested by Sriram. One further question: does ROV stand for "RPKI-based Route Origin Validation” or simply "Route Origin Validation”? We’d like to clarify so that this document will be consistent and so that we can accurately update our abbreviations list (the acronym ROV has not yet been used in the RFC Series). We see instances of both "RPKI-based ROV” and “ROV” in the document. Are any further updates needed for consistency? 

This should be our last question; thank you for your patience!

_______________

Updated XML file:
 https://www.rfc-editor.org/authors/rfc9319.xml

Updated output files:
 https://www.rfc-editor.org/authors/rfc9319.txt
 https://www.rfc-editor.org/authors/rfc9319.pdf
 https://www.rfc-editor.org/authors/rfc9319.html

Diff file showing all changes made during AUTH48:
 https://www.rfc-editor.org/authors/rfc9319-auth48diff.html

Diff files showing all changes:
 https://www.rfc-editor.org/authors/rfc9319-diff.html
 https://www.rfc-editor.org/authors/rfc9319-rfcdiff.html (side-by-side diff)
 https://www.rfc-editor.org/authors/rfc9319-alt-diff.html (shows changes where text was moved/deleted)

For the AUTH48 status of this document, please see:
 https://www.rfc-editor.org/auth48/rfc9319

Thank you,

RFC Editor/rv



> On Sep 29, 2022, at 11:23 PM, Ben Maddison <benm@workonline.africa> wrote:
> 
> Hi Sriram, Rebecca,
> 
> On 09/30, Sriram, Kotikalapudi (Fed) wrote:
>>> We have updated the document. We would like to check with you on one
>>> more thing. RFC 6811 is frequently cited for "RPKI-based Route Origin
>>> Validation (ROV)” and “ROV” in this document; however, RFC 6811
>>> doesn’t include the acronym ROV, though it does discuss “Origin
>>> Validation”. Will this cause any problems for readers?
>> 
> [..]
>> 
>> Just so we are on the same page: I have replaced RPKI-based ROV in the
>> first paragraph with ROV. The abstract includes 'RPKI-based Route
>> Origin Validation (ROV)' and the first use of ROV in the Introduction
>> is the paragraph cited above (Considerations....).
> 
> I have no problem with this change.
> 
> Subject to the above final edit, I approve for RFC publication.
> 
> Cheers,
> 
> Ben