> On May 31, 2017, at 8:47 AM, Barry Leiba <[email protected]> wrote: > > I agree with this. If there's stable documentation on DMARC usage > that we can cite, there's little value in adding our own, which is > likely to end up diverging from the others. > > Does anyone think we *should* proceed with writing this?
A draft has been started on this, with slow progress. The draft aims to fill documentation gaps based on how domain-level policies can impact organizations (across the whole email food chain) and how to best manage impact/interoperability. The original intent of the document was to share operational experience from the PoV of Domain Owners, third party senders, and email receivers/processors. For example, if a third party sender wants to start sending on behalf of Domain Owners, the document would describe how to do this in a ~normal way. The production of the document was supposed to get people to share experience, especially in areas outside of commercial activity. That said, given the WG's history of thin participation, I'm OK with dropping the Usage Guide. The existing gaps in documentation will be filled outside of the IETF. On the one hand I'm a believer that an IETF-produced Usage Guide is better for interoperability than a collection of to-be-published documents spread throughout the Internet. On the other hand, forcing a bunch of people to work on a draft isn't how I like to spend my Internet time. _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
