Personally, I'd have preferred it if the result of using a syntactially
invalid record is undefined, but the existing text was agreed by the WG
and I think it is clear enough. Reject this, please.
On Tue, 27 Oct 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/eid9237/
--------------------------------------
Type: Technical
Reported by: Mehedi Hasan and Tasmim Afroj Lamia <[email protected]>
Section 4.8 (also 4.10.1) says:
Original Text
-------------
Section 4.8:
Syntax errors in the
remainder of the record MUST be discarded in favor of default values
(if any) or ignored outright.
Section 4.10.1:
If a retrieved DMARC Policy Record does not contain a valid "p" tag,
or contains an "sp" or "np" tag that is not valid, then:
* If a "rua" tag is present and contains at least one syntactically
valid reporting URI, the Mail Receiver MUST act as if a record
containing "p=none" was retrieved and continue processing.
* Otherwise, the Mail Receiver applies no DMARC processing to this
message.
Corrected Text
--------------
Section 4.8:
Syntax errors in the remainder of the record MUST be discarded in favor
of default values (if any) or ignored outright, except for invalid "p", "sp",
and "np" values, which are handled as described in Section 4.10.1.
Notes
-----
For a record such as "v=DMARC1; p=reject; sp=bogus" with no "rua", section 4.8 says to ignore the bad
"sp" value, so "p=reject" still applies. Section 4.10.1 says an invalid "sp" means no DMARC
processing at all. The same conflict exists in RFC 7489 (sections 6.3 and 6.6.3). In our tests, implementations split into three
groups: some follow 4.10.1, some ignore the bad tag as in 4.8, and some treat the whole record as an error. We suggest stating
which rule wins.
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]