Doug, you have repeated this argument many times in the working group's development of the document. You're repeating it again during last call. You want DMARC to do more than it's designed for. There is very strong consensus in the working group *not* to expand its scope -- that DMARC is one part of the overall picture, and is not intended to solve all the issues you want to solve. Your view is valid, but strong working group consensus is in the other direction. You are simply "in the rough" here. Barry, DMARC working group chair On Fri, Nov 29, 2024 at 8:55 AM Douglas Foster <dougfoster.emailstandards@xxxxxxxxx> wrote: > > What is the public good that DMARC seeks to address? > > If the goal is to ensure that devastating ransomware attacks are not attributable to messages that impersonate a bank, then the goal has been acheived. > > If the goal is to ensure that devastating ransomware attacks are not attributable to messages that impersonate any sender, then the goal has not been attempted. > > Doug Foster > > > On Fri, Nov 22, 2024 at 12:17 PM The IESG <iesg-secretary@xxxxxxxx> wrote: >> >> >> The IESG has received a request from the Domain-based Message Authentication, >> Reporting & Conformance WG (dmarc) to consider the following document: - >> 'Domain-based Message Authentication, Reporting, and Conformance >> (DMARC) Aggregate Reporting' >> <draft-ietf-dmarc-aggregate-reporting-23.txt> as Proposed Standard >> >> The IESG plans to make a decision in the next few weeks, and solicits final >> comments on this action. Please send substantive comments to the >> last-call@xxxxxxxx mailing lists by 2024-12-06. Exceptionally, comments may >> be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning >> of the Subject line to allow automated sorting. >> >> Abstract >> >> >> Domain-based Message Authentication, Reporting, and Conformance >> (DMARC) allows for Domain Owners to request aggregate reports from >> receivers. This report is an XML document, and contains extensible >> elements that allow for other types of data to be specified later. >> The aggregate reports can be submitted to the Domain Owner's >> specified destination as supported by the receiver. >> >> >> >> >> The file can be obtained via >> https://datatracker.ietf.org/doc/draft-ietf-dmarc-aggregate-reporting/ >> >> >> >> No IPR declarations have been submitted directly on this I-D. >> >> >> The document contains these normative downward references. >> See RFC 3967 for additional information: >> rfc6713: The 'application/zlib' and 'application/gzip' Media Types (Informational - Internet Engineering Task Force (IETF) stream) >> rfc7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC) (Informational - Independent Submission stream) >> >> >> >> >> _______________________________________________ >> dmarc mailing list -- dmarc@xxxxxxxx >> To unsubscribe send an email to dmarc-leave@xxxxxxxx -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx