Dear Mike (AD), This is a reminder that we await your approval of the removal of text from Section 4.1.5. The update can be viewed below and in this file: <https://www.rfc-editor.org/authors/rfc9876-auth48diff.html>. Once we have your approval, we will move this document forward in the publication process.
Section 4.1.5 (removed text): For each of the following example registration requests, one can create a similar instance where the requested registration is for a CoAP Content-Format identifier within the "IETF Review with Expert Review or IESG Approval with Expert Review" range. Likewise, such registrations must not be allowed to succeed. —Files— (please refresh) Updated XML file: https://www.rfc-editor.org/authors/rfc9876.xml Updated output files: https://www.rfc-editor.org/authors/rfc9876.txt https://www.rfc-editor.org/authors/rfc9876.pdf https://www.rfc-editor.org/authors/rfc9876.html Diff files showing all changes made during AUTH48: https://www.rfc-editor.org/authors/rfc9876-auth48diff.html https://www.rfc-editor.org/authors/rfc9876-auth48rfcdiff.html (side by side) Diff files showing all changes: https://www.rfc-editor.org/authors/rfc9876-diff.html https://www.rfc-editor.org/authors/rfc9876-rfcdiff.html (side by side) For the AUTH48 status of this document, please see: https://www.rfc-editor.org/auth48/rfc9876 Best regards, Karen Moore RFC Production Center > On Oct 17, 2025, at 4:27 PM, Karen Moore <[email protected]> wrote: > > Dear Mike (AD), > > This is a reminder that we await your approval of the removal of text from > Section 4.1.5. The update can be viewed below and in this file: > <https://www.rfc-editor.org/authors/rfc9876-auth48diff.html>. Once we have > your approval, we will move this document forward in the publication process. > > Section 4.1.5 (removed text): > For each of the following example registration requests, one can > create a similar instance where the requested registration is for a > CoAP Content-Format identifier within the "IETF Review with Expert > Review or IESG Approval with Expert Review" range. Likewise, such > registrations must not be allowed to succeed. > > > —Files— > (please refresh) > > Updated XML file: > https://www.rfc-editor.org/authors/rfc9876.xml > > Updated output files: > https://www.rfc-editor.org/authors/rfc9876.txt > https://www.rfc-editor.org/authors/rfc9876.pdf > https://www.rfc-editor.org/authors/rfc9876.html > > Diff files showing all changes made during AUTH48: > https://www.rfc-editor.org/authors/rfc9876-auth48diff.html > https://www.rfc-editor.org/authors/rfc9876-auth48rfcdiff.html (side by side) > > Diff files showing all changes: > https://www.rfc-editor.org/authors/rfc9876-diff.html > https://www.rfc-editor.org/authors/rfc9876-rfcdiff.html (side by side) > > For the AUTH48 status of this document, please see: > https://www.rfc-editor.org/auth48/rfc9876 > > Best regards, > > Karen Moore > RFC Production Center -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
