Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-icnrg-pathsteering-07> for your review

Sarah Tarrant <starrant@amsl.com> Wed, 07 February 2024 19:12 UTC

Return-Path: <starrant@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 A069FC14CEFE; Wed, 7 Feb 2024 11:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 ZA-CHdfeWUX0; Wed, 7 Feb 2024 11:12:33 -0800 (PST)
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 9FDB5C14F605; Wed, 7 Feb 2024 11:12:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8EBB2424CD3F; Wed, 7 Feb 2024 11:12:33 -0800 (PST)
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 28KHwZizxS4y; Wed, 7 Feb 2024 11:12:33 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2600:1700:8f1d:4000:1d51:7db1:eaca:c676]) by c8a.amsl.com (Postfix) with ESMTPSA id 21EE4424B427; Wed, 7 Feb 2024 11:12:33 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Sarah Tarrant <starrant@amsl.com>
In-Reply-To: <492EFDF0-91BB-4672-A9B9-31840EF6BF8F@mailbox.org>
Date: Wed, 07 Feb 2024 13:12:22 -0600
Cc: "David R. Oran" <daveoran@orandom.net>, RFC Editor <rfc-editor@rfc-editor.org>, irsg@irtf.org, Dirk Kutscher <ietf@dkutscher.net>, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <31786B89-B03D-447C-8CB3-C33D01C2197F@amsl.com>
References: <20240125225213.4C46119389B0@rfcpa.amsl.com> <EE5883FD-C28B-42D4-8E00-FD4B836C3ADE@orandom.net> <976D5741-0275-46F0-84A1-0026B1F29B1E@amsl.com> <880F1C06-C46F-4554-81FA-CC0CFC37E37D@orandom.net> <75C29AE7-9259-46D8-8DFF-9DA8EBB565CA@amsl.com> <A7BEEED5-F0F6-48AC-8A97-317FF43E1408@orandom.net> <72D9600D-EA18-4352-BD75-36CF39B4B8E0@amsl.com> <A173BC48-6582-4BDB-A5CC-3E81AE561387@orandom.net> <492EFDF0-91BB-4672-A9B9-31840EF6BF8F@mailbox.org>
To: Ilya Moiseenko <iliamo@mailbox.org>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/QNkC4X2NYv1ZqeSal9O2bk6f1WQ>
Subject: Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-icnrg-pathsteering-07> 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, 07 Feb 2024 19:12:38 -0000

All,

We have now received all necessary approvals and consider AUTH48 complete:
https://www.rfc-editor.org/auth48/rfc9531

Thank you for your attention and guidance during the AUTH48 process.

We will move this document forward in the publication process at this time.

Sincerely,
RFC Editor/st

> On Feb 7, 2024, at 11:52 AM, Ilya Moiseenko <iliamo@mailbox.org> wrote:
> 
> Hello Sarah,
> I approve publication.
> 
> Thank you
> Ilya
> 
> 
>> On Feb 2, 2024, at 2:10 PM, David R. Oran <daveoran@orandom.net> wrote:
>> 
>> I approve publication.
>> 
>> One quick note:
>> Two other documents are held waiting on this one for publication:
>> AUTH48: RFC-to-be 9508 <draft-irtf-icnrg-icnping-12> and
>> AUTH48: RFC-to-be 9507 <draft-irtf-icnrg-icntraceroute-11>.
>> 
>> These should go forward for final author approval as well.
>> 
>> Thanks!
>> 
>> 
>> On 2 Feb 2024, at 12:18, Sarah Tarrant wrote:
>> 
>>> Hi David,
>>> 
>>> Thank you for your reply. We have updated the document accordingly.
>>> 
>>> We will await final approvals from each author prior to moving forward in the publication process.
>>> 
>>> The updated files have been posted here (please refresh):
>>> https://www.rfc-editor.org/authors/rfc9531.txt
>>> https://www.rfc-editor.org/authors/rfc9531.pdf
>>> https://www.rfc-editor.org/authors/rfc9531.html
>>> https://www.rfc-editor.org/authors/rfc9531.xml
>>> 
>>> The relevant diff files have been posted here (please refresh):
>>> https://www.rfc-editor.org/authors/rfc9531-diff.html (comprehensive diff)
>>> https://www.rfc-editor.org/authors/rfc9531-auth48diff.html (AUTH48 changes only)
>>> 
>>> Note that it may be necessary for you to refresh your browser to view the most recent version.
>>> 
>>> For the AUTH48 status of this document, please see:
>>> https://www.rfc-editor.org/auth48/rfc9531
>>> 
>>> Thank you,
>>> RFC Editor/st
>>> 
>>>> On Feb 1, 2024, at 10:15 AM, David R. Oran <daveoran@orandom.net> wrote:
>>>> 
>>>> Again, thanks for all the hard work.
>>>> I’ve proofread the document, including a scan for objectionable language.
>>>> I did find a one thing that ought to get fixed:
>>>>  • In section 1.3, s/if successful, receiving a Data containing a path label/if successful, receiving a Data message containing a path label/
>>>> Getting there!
>>>> On 31 Jan 2024, at 13:30, Sarah Tarrant wrote:
>>>> Hi David,
>>>> Thank you for your reply. We have updated the document accordingly.
>>>> We have one followup comment:
>>>>  • Regarding:
>>>> Well, I still think the intended audience won’t be confused, and the parenthetical explanation may be regarded as pedantic. I’d prefer to assume mathematical competence by the reader. Perhaps ask one of your colleagues (or maybe the RFC editor or Independent submission editor if on balance it’s better to spell this out?
>>>> After consulting the other editors, we came to the same conclusion that readers with a background in computer science would understand what “O” stands for, and we will not further update the text.
>>>> Please review the document carefully to ensure satisfaction as we do not make changes once it has been published as an RFC. Contact us with any further updates or with your approval of the document in its current form. We will await approvals from each author prior to moving forward in the publication process
>>>> The updated files have been posted here (please refresh):
>>>> https://www.rfc-editor.org/authors/rfc9531.txt
>>>> https://www.rfc-editor.org/authors/rfc9531.pdf
>>>> https://www.rfc-editor.org/authors/rfc9531.html
>>>> https://www.rfc-editor.org/authors/rfc9531.xml
>>>> The relevant diff files have been posted here (please refresh):
>>>> https://www.rfc-editor.org/authors/rfc9531-diff.html (comprehensive diff)
>>>> https://www.rfc-editor.org/authors/rfc9531-auth48diff.html (AUTH48 changes only)
>>>> Note that it may be necessary for you to refresh your browser to view the most recent version.
>>>> For the AUTH48 status of this document, please see:
>>>> https://www.rfc-editor.org/auth48/rfc9531
>>>> Thank you,
>>>> RFC Editor/st
>>>> DaveO
>> DaveO
>