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

Dave Crocker <dhc@dcrocker.net> Wed, 02 October 2013 17:48 UTC

Return-Path: <dhc@dcrocker.net>
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 8A0A621F9A43 for <ietf@ietfa.amsl.com>; Wed, 2 Oct 2013 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.454
X-Spam-Level:
X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[AWL=1.145, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Bf+iOOUTXTsK for <ietf@ietfa.amsl.com>; Wed, 2 Oct 2013 10:47:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C654B21F9D8B for <ietf@ietf.org>; Wed, 2 Oct 2013 10:45:18 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r92HjAx2014220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Oct 2013 10:45:13 -0700
Message-ID: <524C5B77.9000002@dcrocker.net>
Date: Wed, 02 Oct 2013 10:44:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
In-Reply-To: <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 02 Oct 2013 10:45:13 -0700 (PDT)
Cc: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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 17:48:07 -0000

On 10/2/2013 9:28 AM, John C Klensin wrote:
> After reading the description at the link cited above and
> assuming that "Historic" is actually intended, I wonder,
> procedurally, whether a move to Historic without document other
> than in the tracker is an appropriate substitute for the
> publication of an Applicability Statement that says "not
> recommended" and that explains, at least in the level of detail
> of the tracker entry, why using ADSP is a bad idea.


This suggestion has the dual potential benefits of being inefficient and 
ineffective.

If a spec is Historic, it is redundant to say not recommended.  As in, 
duh...

Even better is that an applicability statement is merely another place 
for the potential implementer to fail to look and understand.

Anyone who fails to understand the implications of Historic (or fails to 
find the correct status) is not going to be better at finding and 
understanding an applicability statement.

ADSP is only worthy of a small effort, to correct its status, to reflect 
its current role in Internet Mail.  Namely, its universal non-use within 
email filtering.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net