Re: [dmarc-ietf] Working Group Last Call on draft-ietf-dmarc-aggregate-reporting-14

2024-03-23 Thread Matthäus Wander
Brotman, Alex wrote on 2024-03-23 19:17: Thanks for the feedback. I believe I've corrected all except - 2.1: "(...) while there MUST be one spf sub-element". At least one according to the XML Schema Definition (might be two, each with a different scope "helo" and "mfrom"). Can we talk about h

Re: [dmarc-ietf] Working Group Last Call on draft-ietf-dmarc-aggregate-reporting-14

2024-03-23 Thread Brotman, Alex
t how this looks in a sample report? -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast > -Original Message- > From: dmarc On Behalf Of Matthäus Wander > Sent: Thursday, March 21, 2024 6:23 PM > To: dmarc@ietf.org > Subject: Re: [dmarc-ietf] Working Group L

Re: [dmarc-ietf] Working Group Last Call on draft-ietf-dmarc-aggregate-reporting-14

2024-03-22 Thread Matthäus Wander
Matthäus Wander wrote on 2024-03-21 23:23: - 2.1: "In most cases, this will be a header_from element, which will contain the 5322.From domain from the message." Add: "There may be an envelope_from element, which contains the RFC5321.MailFrom domain." This paragraph could use some more explanat

Re: [dmarc-ietf] Working Group Last Call on draft-ietf-dmarc-aggregate-reporting-14

2024-03-21 Thread Matthäus Wander
Barry Leiba wrote on 2024-02-29 16:03: This document is also ready for our final look, so this message starts a working group last call for the aggregate reporting document, with the same timing as for the DMARC spec. Please post to the DMARC mailing list by 31 March, giving your last call comme

[dmarc-ietf] Working Group Last Call on draft-ietf-dmarc-aggregate-reporting-14

2024-02-29 Thread Barry Leiba
This document is also ready for our final look, so this message starts a working group last call for the aggregate reporting document, with the same timing as for the DMARC spec. Please post to the DMARC mailing list by 31 March, giving your last call comments (which should include “I read it and