This IETF work affects us all, so I'm reposting here so those with the interest can participate.
"Indirect mail flows" includes but is not limited to mailing lists. "DMARC" is the protocol which Yahoo! and AOL used to unsubscribe thousands of innocent list members in April 2014. This Internet Draft is about to be promoted to RFC, so this is really the last chance to get any changes made. (You can comment on a Request for Comments, but you'll never get one changed. :-) For our purposes, "interoperability" means best practices for both email providers and mailing list operators to avoid reoccurance of that "April Fool's Joke".
If you haven't participated in IETF work before, you might want to run your comments by us (or me personally, if you prefer) before sending them off to the IESG. RFC-ese is not really English. ;-) I'll be happy to provide translation of portions of interest on request.
My personal opinion is that the last draft I looked at (#12) was very good, but the more eyes the better.
Reply-To set to mailman-users, but personal replies to me also welcome. Please don't reply-all. Also, there is no chance that DMARC "p=reject" itself is going away, so let's not rehash that issue.
The IESG writes:
The IESG has received a request from the Domain-based Message Authentication, Reporting & Conformance WG (dmarc) to consider the following document:
- 'Interoperability Issues Between DMARC and Indirect Email Flows' <draft-ietf-dmarc-interoperability-15.txt> as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the email@example.com mailing lists by 2016-06-03. Exceptionally, comments may be sent to firstname.lastname@example.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting.
DMARC introduces a mechanism for expressing domain-level policies and preferences for email message validation, disposition, and reporting. The DMARC mechanism can encounter interoperability issues when messages do not flow directly from the author's administrative domain to the final recipients. Collectively these email flows are referred to as indirect email flows. This document describes interoperability issues between DMARC and indirect email flows. Possible methods for addressing interoperability issues are presented.
The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/
IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/ballot/
No IPR declarations have been submitted directly on this I-D.
dmarc mailing list email@example.com https://www.ietf.org/mailman/listinfo/dmarc