On 4/12/2014 8:17 AM, Miles Fidelman wrote:
Dave Crocker wrote:
On 4/12/2014 5:29 AM, Miles Fidelman wrote:
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.
So what happens to an infrastructure that is operated and governed by
consensus, when a few large players can make major changes to the
infrastructure while ignoring issues that don't directly effect their
interests?
That's an excellent question. Worthy of discussion.
Perhaps oddly, however, it is almost irrelevant to the work of the IETF,
which is creation of technical specification.
Your question is about enforcement, not about creation.
That's an operations issue.
3. A specification cannot be responsible for operators that choose to
deploy something in a way that creates problems documented in the spec.
No. But a standards process can. (E.g., not just anybody can be domain
registry, or enter records into the root nameservers).
That's governed by operations organizations, not the IETF.
At the very least, it strikes me that the IETF should be visibly and
publicly chastising the "ad hoc industry consortium that developed
DMARC" and those who deployed it - as being exceptionally bad actors who:
- roundly ignored issues of major impact in developing the standard
- have deployed it in ways that are causing widespread havoc
- are rather pointedly ignoring that havoc (have you seen anybody from
Yahoo responding?)
I believe the IETF has never done such a thing. I'm pretty sure it
shouldn't.
The more a technical organization delves into public policy and
politics, the less it is a technical organization. Policy and politics
issues come to dominate.
At the least, they confuse perception of the organization.
So while there well might be worthy statements and/or actions to be
taken, when a major actor introduces major disruption, that's not a task
for the IETF.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
