-----Original Message-----
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org [mailto:ietf-dkim-
bounces(_at_)mipassoc(_dot_)org] On Behalf Of Douglas Otis
Sent: Wednesday, May 05, 2010 8:59 AM
To: ietf-dkim(_at_)mipassoc(_dot_)org
Subject: Re: [ietf-dkim] forward to friend, was besides mailing
lists...
+1. Doesn't seem scalable to me.
It is clear that sharing DKIM keys will not scale, determining spoofed
mailing-list by ISPs will not scale, publishing SPF address lists will
not scale. However, since the publishing of hash labels can be
automated or delegated, why would this be something that does not
scale?
There are two points here that don't scale to me:
1) I don't think putting a burden on the users to register every list to which
they might want to subscribe, or become subscribed, is scalable. They will
forget, or do it wrong, or lists will relocate to different domains, or a host
of other scenarios, and then mail will start bouncing and complaints will fly.
2) I don't think that a large organization with security-focused operations
people will think kindly of the idea of user-generated data making its way into
the DNS, whether that's an automated process or not. That doesn't even touch
on the issue that user-generated data is being used to publish some kind of
authorization of the use of that domain by others.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html