Re: [dmarc-ietf] understanding section 7.2

[Alessandro Vesely]

On Wed 27/Jan/2021 21:18:50 +0100 Michael Thomas wrote:

On 1/27/21 12:14 PM, Murray S. Kucherawy wrote:
The schema's already pretty large, and probably has to be, but maybe a 
trivial example report would be reasonable to craft and include?


Yeah, that might do too.



+1.  It can be produced starting from a real report and replacing IPs and 
domain names with exemplifying ones.




I think it's important that it be in section 7.2 though because you should
be able to read that section and understand what the report is and isn't.


The full report should go in an appendix, because it is too long to make sense 
in the middle of text.  Section 7.2 may show the corresponding tabular form[*], 
which provides for a visual summary of fields, and reference the appendix.



Best
Ale
--

[*] A tabular form is showed here:
https://en.wikipedia.org/wiki/DMARC#Aggregate_reports




















___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Re: [dmarc-ietf] understanding section 7.2

[Michael Thomas]

On 1/27/21 12:40 PM, Brotman, Alex wrote:


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.



I opened a ticket on this yesterday. I think it's 102.

Mike



--

Alex Brotman

Sr. Engineer, Anti-Abuse & Messaging Policy

Comcast

*From:* dmarc  *On Behalf Of * Murray S. Kucherawy
*Sent:* Wednesday, January 27, 2021 3:14 PM
*To:* Michael Thomas 
*Cc:* dmarc@ietf.org
*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 <mailto:m...@mtcc.com>> 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
dmarc@ietf.org <mailto:dmarc@ietf.org>
https://www.ietf.org/mailman/listinfo/dmarc

<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$>


___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc
___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Re: [dmarc-ietf] understanding section 7.2

[Brotman, Alex]

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  On Behalf Of Murray S. Kucherawy
Sent: Wednesday, January 27, 2021 3:14 PM
To: Michael Thomas 
Cc: dmarc@ietf.org
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 
mailto:m...@mtcc.com>> 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
dmarc@ietf.org<mailto:dmarc@ietf.org>
https://www.ietf.org/mailman/listinfo/dmarc<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$>
___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Re: [dmarc-ietf] understanding section 7.2

[Michael Thomas]

On 1/27/21 12:14 PM, Murray S. Kucherawy wrote:
The schema's already pretty large, and probably has to be, but maybe a 
trivial example report would be reasonable to craft and include?


Yeah, that might do too. I think it's important that it be in section 
7.2 though because you should be able to read that section and 
understand what the report is and isn't.


Mike




On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas > 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
dmarc@ietf.org 
https://www.ietf.org/mailman/listinfo/dmarc


___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Re: [dmarc-ietf] understanding section 7.2

[Murray S. Kucherawy]

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  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
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>
___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

[dmarc-ietf] understanding section 7.2

[Michael Thomas]

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
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc