Murray, That is on my to-do (though not ticketed). I’m not quite sure how elaborate the example should be, but at least enough to demonstrate a basic report.
-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: dmarc <[email protected]> On Behalf Of Murray S. Kucherawy Sent: Wednesday, January 27, 2021 3:14 PM To: Michael Thomas <[email protected]> Cc: [email protected] Subject: Re: [dmarc-ietf] understanding section 7.2 The schema's already pretty large, and probably has to be, but maybe a trivial example report would be reasonable to craft and include? On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas <[email protected]<mailto:[email protected]>> wrote: So I'm an outsider who has not tried to digest what's going on in the reports until recently so my eyes are fresh. Basically section 7.2 is extremely hard to understand what is in the reports. I know that the XML is what ought to be normative, but a little bit of ascii art could go a long way to helping people understand what the reports do and don't have. I've been staring at the XML all morning trying to understand it and it is very difficult when all you're trying to do is figure out what the reports supply or not. It would be extremely helpful to layout what is in each record for human consumption to just understand what the reports do and don't contain. Mike _______________________________________________ dmarc mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/dmarc<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$>
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
