Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 02 October 2013 21:04 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E13921F9D2A; Wed, 2 Oct 2013 14:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmE5ZyuqcyQF; Wed, 2 Oct 2013 14:04:14 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0D67621F9C05; Wed, 2 Oct 2013 14:04:04 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id l18so6929516wgh.0 for <multiple recipients>; Wed, 02 Oct 2013 14:04:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+M4GBse0SPxFdzjn4kafhorAQDzvlsc31XLD4hy9E54=; b=tnyUah8bXC7MyGhvg61ySZw2SIZYC2+9ez9oD2zCLJDOhgcHVD9u50QPo2ysX0awaK 5YMnUXuAJinBky/9zAH1HqxEA/4nW2oNfeaFJNq1Blo0GuzBf8YmgxfPSSRegEct5MM2 9lOdjNwHrFbqO0IV7SCoef2Dmq6xRaI/duLqp6E97mXTFIg7vFD5nTj3MtoC5dSBwUR1 24xWecz3JJ3oL8BtarJm49d2FxJgLd1pXaPlnzGIU2OJJnPbsOVgBYtXf7cSdD2AI0QI pBR8iUpzYh36o5y11VpnN7gXogYSdsQQwHXla+yxfV6lxYKH/Cnxh8oCXqRDH3P5S6n3 445Q==
MIME-Version: 1.0
X-Received: by 10.180.72.226 with SMTP id g2mr25257483wiv.52.1380747842811; Wed, 02 Oct 2013 14:04:02 -0700 (PDT)
Received: by 10.180.18.202 with HTTP; Wed, 2 Oct 2013 14:04:02 -0700 (PDT)
In-Reply-To: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2013 14:04:02 -0700
Message-ID: <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f46d043890edb1fe4a04e7c86875"
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2013 21:04:21 -0000

On Wed, Oct 2, 2013 at 7:41 AM, The IESG <iesg-secretary@ietf.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