On Wed, Jul 6, 2022 at 7:34 AM <internet-dra...@ietf.org> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Domain-based Message Authentication, > Reporting & Conformance WG of the IETF. > > Title : Domain-based Message Authentication, Reporting, > and Conformance (DMARC) > Authors : Todd M. Herr > John Levine > Filename : draft-ietf-dmarc-dmarcbis-12.txt > Pages : 66 > Date : 2022-07-06 > > Abstract: > This document describes the Domain-based Message Authentication, > Reporting, and Conformance (DMARC) protocol. > > DMARC permits the owner of an email author's domain name to enable > verification of the domain's use, to indicate the Domain Owner's or > Public Suffix Operator's message handling preference regarding failed > verification, and to request reports about use of the domain name. > Mail receiving organizations can use this information when evaluating > handling choices for incoming mail. > > This document obsoletes RFC 7489. >
Speaking as an AD now, you should expect me to complain about the "SHOULD" in Section 4.7. Specifically, since "SHOULD" ultimately permits a choice, we ought to [1] give implementers some guidance about when one might opt not to do what that "SHOULD" says, or in the alternative, make it a "MAY" or "MUST" (probably the latter?). This might also be true of other MUSTard in the document, but since I was just reviewing that section, it jumped out at me. -MSK [1] https://datatracker.ietf.org/doc/html/rfc6919
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
