This erratum is correct. We got the section number wrong. Verified, please.

On Mon, 31 Aug 2026, [email protected] wrote:

The following errata report has been submitted for RFC9989,
"Domain-Based Message Authentication, Reporting, and Conformance (DMARC)"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9150/

--------------------------------------
Type: Editorial
Reported by: VENKAT NOOKALA <[email protected]>

Section 11.6 (also Appendix B.2.3, B.2.4) says:

Original Text
-------------
Section 11.6:
  To avoid abuse by bad actors, reporting addresses generally have to
  be inside the domains about which reports are requested.  To
  accommodate special cases, such as a need to get reports about
  domains that cannot actually receive mail, Section 3 of [RFC9990]
  describes a DNS-based mechanism for validating approved external
  reporting.

Appendix B.2.3:
  Because the address used in the "ruf" tag is outside the
  Organizational Domain in which this record is published, conforming
  Mail Receivers MUST implement additional checks as described in
  Section 3 of [RFC9990].

Appendix B.2.4:
  Intermediaries and other third parties should refer to Section 3 of
  [RFC9990] for the full details of this mechanism.

Corrected Text
--------------
Section 11.6:
  ... Section 4 of [RFC9990] describes a DNS-based mechanism for
  validating approved external reporting.

Appendix B.2.3:
  ... conforming Mail Receivers MUST implement additional checks as
  described in Section 4 of [RFC9990].

Appendix B.2.4:
  Intermediaries and other third parties should refer to Section 4 of
  [RFC9990] for the full details of this mechanism.

Notes
-----
In RFC 9990, Section 3 is "DMARC Feedback" (report format and delivery). The DNS-based verification 
mechanism for external reporting addresses is Section 4, "Verifying External Destinations". All 
three cross-references intend the verification mechanism, so each should read "Section 4 of 
[RFC9990]". The reference in Appendix B.2.3 is normative (MUST), so the incorrect pointer misdirects 
implementers.

Instructions:
-------------
This erratum is currently posted as "Reported". Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9989 (draft-ietf-dmarc-dmarcbis)
--------------------------------------
Title               : Domain-Based Message Authentication, Reporting, and 
Conformance (DMARC)
Publication Date    : May 2026
Author(s)           : T. Herr, Ed., J. Levine, Ed.
Category            : Proposed Standard
Source              : dmarc (art)
Stream              : IETF
Verifying Party     : IESG



Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to