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

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 12 August 2011 14:20 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 D363521F8AB9 for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 07:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 KtxY6BO2ZWMK for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 07:20:35 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 502F95E8001 for <apps-discuss@ietf.org>; Fri, 12 Aug 2011 07:20:35 -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 D1E531ECB41D for <apps-discuss@ietf.org>; Fri, 12 Aug 2011 14:21:12 +0000 (UTC)
Date: Fri, 12 Aug 2011 10:21:10 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20110812142109.GD3724@shinkuro.com>
References: <201108092337.39408.scott@kitterman.com> <201108111807.05405.scott@kitterman.com> <20110812131456.GB3724@shinkuro.com> <201108121000.49202.scott@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <201108121000.49202.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 14:20:36 -0000

On Fri, Aug 12, 2011 at 10:00:48AM -0400, Scott Kitterman wrote:
> 
> It's in wide scale use.  The goal of the current effort is to document that 
> use. 

I don't know why a WG is necessary for that.  There are three
possibilities here.

One is that SPF as specified is in wide scale use, in which case there
is no real protocol work that is needed.  All that is needed is a
report (maybe as an RFC) saying, "This thing was widely deployed.  The
experiment worked."

If, however, the experiment did not work, or bits and pieces of the
RFC are not actually implemented or are implemented differently or are
implemented diffrently by different people, then the new effort can do
one of two things.  One is to move the experimental protocol to the
standards track.  But that automatically requires that one make some
determination about which pieces are going to change, and as Dave
Crocker said somewhere in this thread that is going to attract all
manner of disagreements.  The other is simply to document exactly what
is out there and how things do and do not deviate from the
experimental protocol.  The latter is surely an exercise in research
that delivers an informational document but does not move the protocol
onto the standards track.

In my view, if the goal is to move the protocol to the standards
track, then addressing issues in the protocol as already documented
(and as actually deployed) has to be an open possibility.  If that's
not the goal, then I have no objection.  I don't see what the value
would be in moving something to the standards track without being
willing to undertake standards work on it.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com