Re: [apps-discuss] Updating the status of SPF

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 12 August 2011 16:18 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFAE21F86BE for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 09:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level:
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599]
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 zO+unUFfA58K for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 09:18:27 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id DAD1721F86AF for <apps-discuss@ietf.org>; Fri, 12 Aug 2011 09:18:27 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id D09E71ECB41D for <apps-discuss@ietf.org>; Fri, 12 Aug 2011 16:19:05 +0000 (UTC)
Date: Fri, 12 Aug 2011 12:19:03 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20110812161902.GH3724@shinkuro.com>
References: <201108092337.39408.scott@kitterman.com> <201108121000.49202.scott@kitterman.com> <20110812142109.GD3724@shinkuro.com> <201108121138.57806.scott@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <201108121138.57806.scott@kitterman.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [apps-discuss] Updating the status of SPF
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 16:18:28 -0000

On Fri, Aug 12, 2011 at 11:38:57AM -0400, Scott Kitterman wrote:

> My view is that the experiment was largely successful and only minor changes 
> based on this experience are necessary.

This is the problem I'm focussed on, however: once you say, "My
changes are minor, $someone's are not in scope," you basically open up
the protocol by having to debate the values of "my" and "minor" (and,
too often I find, "changes").

I really don't have a dog in this race: I don't care about SPF, and
the TXT battle was lost a long time ago.  I'm just saying that, if the
goal really is supposed to be, "Just document what's happened," you
don't need a WG and you don't need to move tracks.  You need a
document that outlines what happened, period.  That will more readily
achieve the goal of documenting actual existing practice and getting
the document out in a reasonable time frame.  Everything else
effectively means that you have to deal with all the issues Dave
Crocker correctly identified.

At the same time, I am strongly opposed, on process grounds, to a WG
whose task it is to move a protocol from the experimental track to the
standards track without facing any of the questions about whether the
experiment worked, the extent of that working, and the trade-offs that
might have been acceptable in an experiment but that are not
acceptable for anything we might call a standard.  If there is to be
any distinction at all between these tracks, then those questions must
be acceptable when changing.  Otherwise, we get an experimental track
that is just a new level in the 3 (soon to be (3-n)) level standards
track we already have.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com