On Wed, Oct 2, 2013 at 7:41 AM, The IESG <iesg-secretary(_at_)ietf(_dot_)org>
wrote:
The IESG has received a request from an individual participant to make
the following status changes:
- RFC5617 from Proposed Standard to Historic
The supporting document for this request can be found here:
http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
[...]
I support this change, for the reasons articulated in the request and in
this thread.
I am the lead developer and maintainer of OpenDKIM, an open source
implementation of DKIM and related standards, including VBR, ADSP, the
recent REPUTE work, and some others. It is widely deployed, including use
at a few of the largest operators. An informal survey was done on one of
the mailing lists where this package is supported, asking which operators
do ADSP queries and which act upon the results. I have so far only
received a half dozen answers to this, but the consensus among them is
clear: All of the respondents either do not check ADSP, or check it but do
nothing with the results. One operator puts disposition of messages based
on ADSP results into the hands of its users, but no statistics were offered
about how many of these users have ADSP-based filtering enabled. That same
operator intends to remove that capability once this status change goes
into effect.
-MSK