Hi Robert and Andy*, *Andy - As the AD, please review and approve of the following updates: - Section 1: updated text - Section 3: removed text
See this diff file: https://www.rfc-editor.org/authors/rfc9982-auth48diff.html Robert - Thank you for your reply. We have updated as requested. If you have any further updates, please reply in this email thread with an explicit list of changes or an updated XML file rather than submitting a new version in Datatracker. The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9982.xml https://www.rfc-editor.org/authors/rfc9982.txt https://www.rfc-editor.org/authors/rfc9982.html https://www.rfc-editor.org/authors/rfc9982.pdf The relevant diff files have been posted here: https://www.rfc-editor.org/authors/rfc9982-diff.html (comprehensive diff) https://www.rfc-editor.org/authors/rfc9982-auth48diff.html (AUTH48 changes) https://www.rfc-editor.org/authors/rfc9982-auth48rfcdiff.html (AUTH48 changes side by side) Please review the document carefully and contact us with any further updates you may have. Note that we do not make changes once a document is published as an RFC. We will await approvals from each party listed on the AUTH48 status page below prior to moving this document forward in the publication process. For the AUTH48 status of this document, please see: https://www.rfc-editor.org/auth48/rfc9982 Thank you, Alanna Paloma RFC Production Center > On May 19, 2026, at 4:41 AM, Robert Stepanek > <[email protected]> wrote: > > Dear Editors, > > we just submitted new version draft-ietf-calext-jscontact-uid-08. It > rephrases some text and removes a potentially confusing remark. > > On Wed, May 13, 2026, at 12:20 AM, [email protected] wrote: >> 1) <!-- [rfced] Please insert any keywords (beyond those that appear in >> the title) for use on https://www.rfc-editor.org/search. --> > > > Done. > >> >> 2) <!-- [rfced] FYI - We have added expansions for the following >> abbreviations >> per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each >> >> expansion in the document carefully to ensure correctness. >> >> JSON Meta Application Protocol (JMAP) >> Registration Data Access Protocol (RDAP) >> --> > > > All correct. > >> 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. Updates of this nature typically >> result in more precise language, which is helpful for readers. >> >> Note that our script did not flag any words in particular, but this should >> still be reviewed as a best practice. >> --> > > > Reviewed. > > Thanks, > Robert > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
