Hello Todd and John,
We have merged the updates.
Additionally, we have further updated the ABNF in Section 4.8, as the
previously suggested update was 1 character over the 72-character limit.
Current:
dmarc-urilist = (dmarc-uri / obs-dmarc-uri)
*(*WSP "," *WSP (dmarc-uri / obs-dmarc-uri))
Please review the XML file and its TXT, HTML, and PDF outputs, and let us know
if any changes are required or if you approve the RFC for publication. We
consider this your final assent that the document is ready for publication. To
request changes or approve your RFC for publication, please reply to this
email. Please use ‘REPLY ALL’, as all the parties CCed on this message need to
see your approval.
XML file:
https://www.rfc-editor.org/authors/rfc9989.xml
Output files:
https://www.rfc-editor.org/authors/rfc9989.txt
https://www.rfc-editor.org/authors/rfc9989.html
https://www.rfc-editor.org/authors/rfc9989.pdf
Comprehensive diff file of the text:
https://www.rfc-editor.org/authors/rfc9989-diff.html
https://www.rfc-editor.org/authors/rfc9989-rfcdiff.html (side by side)
For the AUTH48 status of this document, please see:
https://www.rfc-editor.org/auth48/rfc9989
Thank you,
Alanna Paloma
RFC Production Center
> On May 12, 2026, at 11:22 AM, [email protected] wrote:
>
> *****IMPORTANT*****
>
> Updated 2026/05/12
>
> RFC Author(s):
> --------------
>
> Your document has now entered AUTH48.
>
> AUTH48 is being handled in GitHub as part of the GitHub pilot test (see
> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test).
>
>
> Your document is available for review at:
> https://github.com/rfc-editor/AUTH48-rfc9989
>
> Please do the following:
>
> a) accept your invitations to join the repo as collaborators.
>
> b) see the README for details on the AUTH48 process:
> https://github.com/rfc-editor/AUTH48-rfc9989/blob/Approved/README.md
>
> c) review and resolve the issues:
> https://github.com/rfc-editor/AUTH48-rfc9989/issues
>
> Once the content is stable in GitHub, we will provide the updated XML file
> and the output files for review and approval.
>
> You and your coauthors are responsible for engaging other parties
> (e.g., Contributors or Working Group) as necessary before providing
> your approval.
>
> Once the document has been reviewed and approved by all of the authors,
> it will be published as an RFC. If an author is no longer
> available, there are several remedies available as listed in the
> FAQ (https://www.rfc-editor.org/faq/).
>
> Please let us know if you have any questions.
>
> Thank you for your cooperation,
>
> RFC Editor
>
> --------------------------------------
> RFC 9989 (draft-ietf-dmarc-dmarcbis-41)
>
> Title : Domain-based Message Authentication, Reporting, and
> Conformance (DMARC)
> Author(s) : T. Herr, Ed., J. Levine, Ed.
> WG Chair(s) : Barry Leiba, Seth Blank
> Area Director(s) : Andy Newton, Charles Eckel
>
>
--
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
