Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Brotman, Alex
ones Sent: Thursday, March 9, 2023 2:49 PM To: dmarc@ietf.org Subject: Re: [dmarc-ietf] Version in aggregate report On 3/9/23 11:45, Tomki Camp wrote: I think that's a good idea. Mike Jones from Fortra (ne Agari) also expressed concern during M3AAWG 57 about problems for data analysis to be

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Steven M Jones
On 3/9/23 11:45, Tomki Camp wrote: I think that's a good idea. Mike Jones from Fortra (ne Agari) also expressed concern during M3AAWG 57 about problems for data analysis to be able to determine how a specific receiver's result was achieved, with the discovery methodology doubling. An XML

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Tomki Camp
0" maxOccurs="1"/> > > > > The excepted values being the enumerated discovery mechanisms (e.g. > something like "hop", "treewalk"). > > > > Thoughts? > > > > - Trent > > > > > > > > *From: *dmarc

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread John Levine
It appears that Trent Adams said: >-=-=-=-=-=- > > >Alex - > >I think that the difference comes down to an inference made by the report >analyst (and assuming enough data to make an >informed guess) vs. the report generator expressly stating the mechanism they >used. > >IMO, it makes sense to

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Dotzero
*From: *"Brotman, Alex" > *Date: *Thursday, March 9, 2023 at 11:37 AM > *To: *Trent Adams , "dmarc@ietf.org" < > dmarc@ietf.org> > *Subject: *RE: [dmarc-ietf] Version in aggregate report > > > > Trent, I’m not entirely opposed to the idea, though I w

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Trent Adams
Ei_n_ok=187s From: "Brotman, Alex" Date: Thursday, March 9, 2023 at 11:37 AM To: Trent Adams , "dmarc@ietf.org" Subject: RE: [dmarc-ietf] Version in aggregate report Trent, I’m not entirely opposed to the idea, though I wonder if it’s necessary. It seems like if

Re: [dmarc-ietf] Version in aggregate report

2023-03-09 Thread Brotman, Alex
in the report to point at, we can create a field. Thoughts from others? -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: Trent Adams Sent: Wednesday, March 8, 2023 11:44 AM To: Brotman, Alex ; dmarc@ietf.org Subject: Re: [dmarc-ietf] Version in aggregate report Alex -

Re: [dmarc-ietf] Version in aggregate report

2023-03-08 Thread Trent Adams
erhaps something like: The excepted values being the enumerated discovery mechanisms (e.g. something like "hop", "treewalk"). Thoughts? - Trent From: dmarc on behalf of "Brotman, Alex" Date: Wednesday, March 8, 2023 at 9:25 AM To: "dmarc@ie

[dmarc-ietf] Version in aggregate report

2023-03-08 Thread Brotman, Alex
While reviewing something in the aggregate doc, I came across this bit in the XML specification. Unless I've missed something, we're not incrementing the version in the DMARC DNS record. So, if we're not changing that DNS record, obviously this "version" string has less meaning. The