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

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Sat, 13 August 2011 17:36 UTC

Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.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 2FD3521F8563 for <apps-discuss@ietfa.amsl.com>; Sat, 13 Aug 2011 10:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.718
X-Spam-Level:
X-Spam-Status: No, score=-102.718 tagged_above=-999 required=5 tests=[AWL=0.381, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 guMUI3UvzN8q for <apps-discuss@ietfa.amsl.com>; Sat, 13 Aug 2011 10:36:10 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4816A21F854D for <apps-discuss@ietf.org>; Sat, 13 Aug 2011 10:36:10 -0700 (PDT)
Received: by ywm21 with SMTP id 21so2835899ywm.31 for <apps-discuss@ietf.org>; Sat, 13 Aug 2011 10:36:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wIIi+nFatDnhhLu3hw90K1ouPdnbmbvDyjattwkPFU0=; b=Bf3hPo9CyqkqDbGEuP3mdDLYVuMs7eZU/P6/LChiVe2ksRV8RYbCXNCLGYh8yULUY8 vqxA6hKQFWajoxq5fb5DudqiTkkBPCbGdCnW/RQ26lN9frVzkG+sfsLmU7o6+uvWhgPE elS2V5AwBInZTmNE7RuJThYSKT3z8aks4gNzc=
Received: by 10.143.20.12 with SMTP id x12mr971134wfi.105.1313257006338; Sat, 13 Aug 2011 10:36:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.157.2 with HTTP; Sat, 13 Aug 2011 10:36:26 -0700 (PDT)
In-Reply-To: <20110812222438.GL2625@shinkuro.com>
References: <201108092337.39408.scott@kitterman.com> <201108121138.57806.scott@kitterman.com> <20110812161902.GH3724@shinkuro.com> <201108121729.09648.scott@kitterman.com> <20110812222438.GL2625@shinkuro.com>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 13 Aug 2011 19:36:26 +0200
Message-ID: <CAHhFybrhbjHoNuA3D0_7mrzVmWeLq1JROH=n+K_n7koEBWQeNQ@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: apps-discuss@ietf.org
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: Sat, 13 Aug 2011 17:36:11 -0000

On 13 August 2011 00:24, Andrew Sullivan wrote:

> This is exactly the process objection I have.

Hi, I'm not sure how obvious this is for others, but SPF
is completely unsuited as an "example" or "precedence" in
more general two vs. three steps procedural discussions.

When RFC 4408 was published as an "IETF experiment" SPF
was already widely deployed, and the RFC was in fact the
result of experiments based on earlier Internet drafts,
and submitted as a "proposed standard".

For let's say "non-technical reasons" it ended up as an
experimental RFC, and anybody interested in the details
can dig through old MARID and spf-discuss mail archives,
or try to reconstruct the SPF history from footnotes in
the appeal to the IAB -- NOT RECOMMENDED unless you have
a grim sense of humour.

In other words, SPF is not really the first incarnation
of a new "four steps" procedure, but there are certainly
errata justifying a 4408bis, and I'd be interested to
work on that if it is for "standard tracks".  Otherwise
I'd say that implementors should find the errata page on
openspf.org, its URL is not affected by the "status" of
erratum 994.

-Frank