-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast
> -----Original Message----- > From: John Levine <[email protected]> > Sent: Monday, August 19, 2024 2:05 PM > To: [email protected] > Cc: Brotman, Alex <[email protected]> > Subject: [EXTERNAL] Re: [dmarc-ietf] Re: New Version Notification for > draft-ietf- > dmarc-aggregate-reporting-17.txt > > It appears that Brotman, Alex <[email protected]> said: > >Hey folks > > > >I believe I have mostly addressed Barry's concerns that he sent to the list > >last > week. > > > >There was a note about two of the policy override options (section > >2.1.5), "forwarded", and "trusted_forwarder". They are currently next to > >each > other in the draft, though, I don't believe we need both. If someone else > believes > there is some difference that can be more properly illustrated, I'm happy to > take > that language. > >Otherwise, I'd likely remove "forwarded", and just leave the other with its > current description. > > > >https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf > >-dmarc-aggregate- > reporting/__;!!CQl3mcHX2A!FcMIaqE8cIJxQVp3heiHedrQKnBt > >ENk3MHc3a6DdTNyDgyt770lVqvh3Qyh-5_uKxa7aUUOZAE_gJ6nU$ > > I agree that forwarded and trusted_forwarder are redundant > > In the subject line exxample in 2.6.2, the Report-ID is not a ridtxt. > That example was wrong in 7489. Removed one of the forward options, and updated the ridtxt on the Subject example. > > In 6.2 it says there is no PII in aggregate reports. If a domain has few > enough > users, there can in practice be PII but I wouldn't worry about it, since > that's an > issue for every use of the domain, not just in DMARC. > I feel like this was discussed on the list, and we decided that there wasn't a practical issue. I can rework it to note the above if you believe the document benefits. > I think the XML schema is OK, but as always more people lo oking at it would be > better. > > R's, > John _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
