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

Scott Kitterman <scott@kitterman.com> Fri, 12 August 2011 14:00 UTC

Return-Path: <scott@kitterman.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 5056521F8834 for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 07:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 j48EBB7RgowD for <apps-discuss@ietfa.amsl.com>; Fri, 12 Aug 2011 07:00:16 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id A44F721F881C for <apps-discuss@ietf.org>; Fri, 12 Aug 2011 07:00:16 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id 96B6638C12D; Fri, 12 Aug 2011 10:00:51 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1313157651; bh=wx/BkCE5xa2HoaFc1nOX+fqyBcu94WV+rrrMdGitW8w=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=ECfPdVbFRYBg1PeFrtIteelF/ucVT8CmcQbFPzFYP1DKWpVazGke3X3dqDjwNrIwr TvWqPPiiUXkM/Qo0GVmiTShs3vYNt72aHdqGCro/giPGk/RH9xoASluWmT2lf8ONph tbTY+hF4wFKwI19w1Y8hMiBPfeTHyupckKxUiyZU=
From: Scott Kitterman <scott@kitterman.com>
To: apps-discuss@ietf.org
Date: Fri, 12 Aug 2011 10:00:48 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-10-generic-pae; KDE/4.6.2; i686; ; )
References: <201108092337.39408.scott@kitterman.com> <201108111807.05405.scott@kitterman.com> <20110812131456.GB3724@shinkuro.com>
In-Reply-To: <20110812131456.GB3724@shinkuro.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201108121000.49202.scott@kitterman.com>
X-AV-Checked: ClamAV using ClamSMTP
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:00:17 -0000

On Friday, August 12, 2011 09:14:57 AM Andrew Sullivan wrote:
> On Thu, Aug 11, 2011 at 06:07:04PM -0400, Scott Kitterman wrote:
> > I feel strongly that the 4408bis effort we are discussing now should be a
> > minimal/backwards compatible_unless_it_is_impossible update.  Once that
> > is complete there is a backlog of incompatible design ideas for
> > simplifying and improving SPF.  In that context I think moving to Type
> > SPF only makes a lot of sense and should be considered.  I don't want to
> > get that mixed in with the current effort.
> 
> I don't have a strong feeling about this, but why is that a better
> strategy?  If the goal is to move SPF off the EXPERIMENTAL track, then
> surely the time to make changes to the protocol is when you move it
> and determine the extent to which the experiment worked or didn't?
> Cf. the current effort in the EAI WG.

It's in wide scale use.  The goal of the current effort is to document that 
use. 

Scott K