I've volunteered to shepherd this document. I've reviewed -17 and have the following feedback on the current content. Most of it is nits, so hopefully resolution here is easy. I'll upload my shepherd writeup to the datatracker after I send this to the list.
1. We interchangeably use "mail" and "messages" throughout this document (and probably others) to describe email flows and messages. I wonder if it's possible to converge on one. Probably not, since the "M" in "DMARC" stands for "Message", but some of the imported terms use "Mail", but I thought I'd mention it. 2. In the Abstract, suggest changing "using" to "that use". 3. In Section 1: s/On the one/On one/. In fact, I suggest rewriting that whole sentence: On one hand, they are meant to aid in cases where a Domain Owner wishes to determine the cause of failures that were part of aggregate reports (see [I-D.ietf-dmarc-aggregate-reporting]). 4. Also in Section 1, where the admonition about PII is, I suggest a forward reference to Section 7. 5. In Section 2, replace Paragraph 4 with: When a Domain Owner requests failure reports for the purpose of forensic analysis, and the Mail Receiver is willing to provide such reports, the Mail Receiver generates and sends a message using the format described in [RFC6591] but as modified in Section 4 of this document. 6. Right below that, replace Paragraph 5 with: The destination(s) to which failure reports are sent, and options for when they will be sent, are defined by the "ruf" and "fo" tags as defined in Section 4.7 of [I-D.ietf-dmarc-dmarcbis]. 7. In Section 3, s/the fo= tag/the "fo" tag/ to be consistent with other tag references in this document. 8. Also in Section 3, some explanation of why that RECOMMENDED is there would be good to include (or remove it if we can't justify it in terms of interoperability). 9. Section 6.1 should mention that the sub-registry to be updated is part of the "Messaging Abuse Reporting Format (MARF) Parameters" registry group. 10. In Section 7, "Always transmit reports only over secure channels." could do without the word "only". 11. In Section 7.3, s/urls/URIs/ and s/mx servers/MX servers/. Actually I'm not sure we should include "MX" without explaining what we mean there. -MSK
_______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
