[auth48] Re: [AD] AUTH48: RFC-to-be 9770 for your review

2025-04-15 Thread RFC Editor via auth48archive
Authors and *AD, [AD - please review and weigh in on Question 21.] While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file. 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15)

[auth48] Re: AUTH48: RFC-to-be 9728 for your review

2025-04-15 Thread Michael Jones via auth48archive
Thank you, Lynne. Please record in https://www.rfc-editor.org/auth48/rfc9728 that I approve of the publication of the current draft as RFC 9728. Phil, Aaron, do you concur? Thanks all, -- Mike -Original Message- From: Lynn

[auth48] Re: AUTH48: RFC-to-be 9728 for your review

2025-04-15 Thread Phil Hunt via auth48archive
I concur Phil > On Apr 15, 2025, at 10:09 PM, Michael Jones > wrote: > > Thank you, Lynne. Please record in > https://www.rfc-editor.org/auth48/rfc9728 that I approve of the publication > of the current draft as RFC 9728. > > Phil, Aaron, do you concur? > >

[auth48] Re: AUTH48: RFC-to-be 9728 for your review

2025-04-15 Thread Lynne Bartholomew via auth48archive
Hi, Mike. Thanks for your replies! We have updated this document per your notes below. Apologies for the missing space before the email address; thank you for catching that! We also removed the " From: Michael Jones > Sent: Monday, April 14, 2025 5:29 PM > To: 'Lynne Bartholomew' ; Aaron Pare

[auth48] Re: AUTH48: RFC-to-be 9767 for your review

2025-04-15 Thread Fabien Imbault via auth48archive
Hi there, I have no idea, my email account is perfectly fine and I do receive ietf notifications. Yet if that's really an issue you may use fabien.imba...@gmail.com if needed. Best regards Fabien On Mon, 14 Apr 2025, 21:06 Justin Richer, wrote: > Hi Karen, > > This happened recently with RFC963

[auth48] Re: AUTH48: RFC-to-be 9750 for your review

2025-04-15 Thread Lynne Bartholomew via auth48archive
Great! So noted (https://www.rfc-editor.org/auth48/rfc9750). We will prepare this document for publication shortly. Thank you! RFC Editor/lb > On Apr 15, 2025, at 10:53 AM, Eric Rescorla wrote: > > Approved. > > On Tue, Apr 15, 2025 at 10:01 AM Lynne Bartholomew > wrote: > Hi, Srinivas a

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-04-15 Thread Madison Church via auth48archive
Hi Enrico, Thank you for your reply! We have updated the document as requested. Please take a moment to review the changes and ensure they appear as desired. For the following: >> 4) We note that the ISO reference has been withdrawn and is no longer >> available. There are two updated versions

[auth48] Re: AUTH48: RFC-to-be 9750 for your review

2025-04-15 Thread Lynne Bartholomew via auth48archive
Hi, Srinivas and Eric. Srinivas, we have noted your approval on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9750 Eric, here are the latest files. No new iteration. Please refresh your browser: https://www.rfc-editor.org/authors/rfc9750.txt https://www.rfc-editor.org

[auth48] Re: [AD] [C507] AUTH48 Questions: RFC-to-be 9665 and RFC-to-be 9664

2025-04-15 Thread Eric Vyncke (evyncke) via auth48archive
Dear Sarah, dear RFC Editor, Just checking whether the authors, the AD (or the IANA) have still some pending actions before the publication of these two RFCs ? Regards -éric On 09/04/2025, 06:28, "Stuart Cheshire" wrote: On Apr 8, 2025, at 13:42, Sarah Tarrant mailto:starr...@staff.rfc-edit

[auth48] Re: AUTH48: RFC-to-be 9728 for your review

2025-04-15 Thread Michael Jones via auth48archive
Lynne, also please remove the " >> > Please use this wording, as we identified another ambiguity in the previous > wording: > > These values, such as the jwks_uri (see Section 2), may be > used with other specifications; for example, the public keys published > in the jwks_uri can be used to verif