I’m not sure what the relevance of this particular debate is, but in hopes of moving us forward, I offer another data point.
Please remember that you can deploy DMARC and get exactly the desired result from your DMARC deployment, without deploying any DKIM infrastructure. Example: you can push a p=reject on a domain that never sends mail. You can push any p= value for a domain that is only “protected” by SPF records, even one that is in use, and get exactly the desired result. DKIM is of course required to achieve the desired result for most mail flows, but DKIM it is not in any way required for all successful deployments of DMARC. Given that fact, perhaps we can stop debating whether or not DMARC is a DKIM Policy Framework. But what was the point of that debate in the first place? If we all agreed that DMARC was a DKIM Policy Framework, what outcome would that have brought us closer to? I suspect there was a purpose for that argument that might still be relevant to our work even though the argument doesn’t seem to be supported, but I’m not seeing it yet. -Brett > On Oct 27, 2014, at 4:58 PM, Dave Crocker <d...@dcrocker.net> wrote: > > On 10/27/2014 12:23 PM, J. Gomez wrote: >> On Saturday, October 25, 2014 5:57 PM [GMT+1=CET], Dave Crocker >> wrote: >>> DMARC defines DMARC-related 'policies'. >>> >>> It does not affect DKIM in any way. It is an overlay to DKIM >>> and/or SPF use. >> >> DMARC defines DMARC-related 'policies' which are an overlay on DKIM, >> which to me could be also aptly phrased as "DMARC creates a policy >> framework for DKIM", and more succintly "DMARC is a DKIM Policy >> Framework". >> >> Yes, DMARC does not change DKIM de-iure. But also, yes, DMARC does >> bring POLICY to DKIM. > > No it does not. > > The relationship between DMARC and DKIM (and SPF) is like the > relationship between TCP and IP. TCP does not 'bring reliability and > congestion control to IP'. Rather, TCP /uses/ IP as a transfer > component to the TCP reliability and congestion control framework that > TCP creates. > > DMARC creates an authorization framework for the rfc5322.From (author) > field. It uses DKIM and SPF for some authentication components to the > DMARC framework. > > This is a fundamentally different relationship than what you are > asserting. Your statement confuses roles and relationships. > > >> The truth here is that DMARC is going to be a de-facto DKIM 2.0. And > > Nope. > > > d/ > > -- > Dave Crocker > Brandenburg InternetWorking > bbiw.net > > _______________________________________________ > 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
