On 4/12/2014 5:29 AM, Miles Fidelman wrote:
It does strike me that DMARC, which is currently an internet-draft, not even an RFC, is causing incredible disruption by its adoption, by a few very large players. Methinks this indicates a serious problem, and raises some questions about what measures might be taken when a big player breaks the Internet by not playing nice. It sure seems that IETF should play a role in this.
1. DMARC was developed by an ad hoc industry consortium. It is already deployed well enough to cover an estminated 60% of the world's email traffic. As such, it's status with the IETF is obviously not a gating factor. So the "not even an RFC" has some formal import, but limited practical import.
2. The spec is clear about how it works and what the implications are. The issue with mailing lists is well-documented.
3. A specification cannot be responsible for operators that choose to deploy something in a way that creates problems documented in the spec.
4. You don't say what you feel the IETF should do, nor is it obvious to me what role the IETF can reasonably have for this sort of deployment issue.
d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
