Great question. I’ve been around since the beginning as a very strong DKIM Policy advocate, watching everything, my dumb attempt to summarize:
1) The idea of “reporting” was considered a testing thing. Redundant,. DomainKeys and DKIM had -t test keys. I believed and others as well, felt reporting was an attack vector. I included reporting ideas in DSAP but the format was not defined. The section was left TBD. 2) Murray was working on reporting methods with a format. He was obviously filling a need out there. 3) I did not hear of anyone honoring ADSP rejects because of the known indirect mail problems. 4) ADSP was abandoned and replaced with Super ADSP aka DMARC which introduced a reporting and compliance concept. It had a strong policy idea. 5) I totally under estimated the administrator direct for reports. But I still didn’t believe it in. It’s for testing only, right? 6) I did not hear of anyone rejecting on DMARC p=reject. So it was just about Reporting & Conformance. 7) Then YAHOO.COM <http://yahoo.com/>, the patented inventor of this all this starting with DomainKeys, the first with a built-in `o=` tag policy concept, was the first big system to honor published DMARC strict policies. 8) Now DMARC become about Handling and proper SMTP integration with SPF. The end! Happy July 4th Weekend. Be safe!! — HLS > On Jun 30, 2023, at 2:22 PM, Todd Herr > <todd.herr=40valimail....@dmarc.ietf.org> wrote: > > Genuine curiosity question here for those who were around at the beginning... > > Why is the mechanism called "Domain-based Message Authentication, Reporting, > and Conformance" and not "Domain-based Message Authentication, Reporting, and > Disposition"? Perhaps a better question, why is "conformance" in the name of > the mechanism? > > I ask because I'm writing up some stuff for internal use, and I got curious > as to how conformance is defined or explained in RFC 7489, and well, it's > not. The word appears five times in RFC 7489, and each occurrence is in the > context of spelling out the full name of the mechanism. > > I am not looking to change the name of the mechanism; I'm just genuinely > curious how the name was arrived at. > > -- > Todd Herr | Technical Director, Standards & Ecosystem > e: todd.h...@valimail.com <mailto:todd.h...@valimail.com> > p: 703-220-4153 > m: 703.220.4153 > > This email and all data transmitted with it contains confidential and/or > proprietary information intended solely for the use of individual(s) > authorized to receive it. If you are not an intended and authorized recipient > you are hereby notified of any use, disclosure, copying or distribution of > the information included in this transmission is prohibited and may be > unlawful. Please immediately notify the sender by replying to this email and > then delete it from your system. > _______________________________________________ > 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
