In article <caozaafouyft5f7jjxi57chbzjwpu1nwb_xup5ipjpxu5gu2...@mail.gmail.com> you write: >-=-=-=-=-=- >Aggregate reports and failure reports get used in wholly different manners, >have fundamentally different use cases, are implemented in wildly different >ways, and have completely different privacy and security considerations.
All true, but the actual specs overlap quite a lot. For example, where does section 7.1 about verifying external destinations go? If the answer is that it's copied into two documents, that is bad. I think we've seen that for failure reporting there is nothing to change beyond updating the privacy considerations, so leaving all the reporting in one document is unlikely to cause schedule problems. R's, John _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
