On Mon 13/Jan/2025 03:34:28 +0100 Brotman, Alex wrote:
Please take a moment and give it a review.
In Section 2.1, a report contains *The DMARC policy discovered and applied, if
any*. Shouldn't that be *discovered and considered for application*? There is
even a "reason" for not applying it...
*The number of successful authentications*? There is no such field.
The sentence *A single report MUST contain data for one policy configuration*
is still there. The rest of that paragraph (If multiple configurations...)
should be moved to Section 2.1.1.5.
In Section 2.1.1.4, the criterion for defining periods is still not defined.
I'd re-propose what I wrote last December:
The start and end of reporting periods are chosen to obtain a partition
of time, such that each instant of time belongs to exactly one period.
Empty reports must not be sent.
In Section 2.1.1.8, the phrase *how many e-mails was received from it* is
inexact. "count" specifies only the e-mails matching the auth_results of the
parent element.
In Section 2.1.1.11, *If validation is attempted for any DKIM signature, the
results MUST be included* is an excessive requirement.
Section 2.1.6 should be merged in Section 2.1.1.14, for a smooth reading
experience.
Best
Ale
--
_______________________________________________
dmarc mailing list -- dmarc@ietf.org
To unsubscribe send an email to dmarc-le...@ietf.org
