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

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 09 August 2011 11:02 UTC

Return-Path: <alexey.melnikov@isode.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 98BBB21F8892 for <apps-discuss@ietfa.amsl.com>; Tue, 9 Aug 2011 04:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level:
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 N37derwAVuEZ for <apps-discuss@ietfa.amsl.com>; Tue, 9 Aug 2011 04:02:43 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id DE69C21F88B6 for <apps-discuss@ietf.org>; Tue, 9 Aug 2011 04:02:42 -0700 (PDT)
Received: from [188.28.117.11] (188.28.117.11.threembb.co.uk [188.28.117.11]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TkET6wBd6TYD@rufus.isode.com>; Tue, 9 Aug 2011 12:03:08 +0100
Message-ID: <4E4113F8.6060807@isode.com>
Date: Tue, 09 Aug 2011 12:03:20 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: Barry Leiba <barryleiba@computer.org>, "Murray S. Kucherawy" <msk@cloudmark.com>
References: <AcxV+CxT9WxP2wTLTNWpQ3LXOor+nw==> <F5833273385BB34F99288B3648C4F06F13512DF606@EXCH-C2.corp.cloudmark.com> <CAC4RtVCncUmdM+g8c+tTBGMnXHtL5+5hGwNF7+n14sDbBst8WQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCncUmdM+g8c+tTBGMnXHtL5+5hGwNF7+n14sDbBst8WQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-transfer-encoding: quoted-printable
Cc: "apps-discuss@ietf.org" <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: Tue, 09 Aug 2011 11:02:43 -0000

Barry Leiba wrote:
>> A participant in another WG has expressed interest in republishing SPF
>> (RFC4408) on the standards track.  This clearly and historically falls into
>> the APPS realm.  The work is probably in need of a WG home, and with YAM
>> leaning toward spinning down, this is the next best place to ask.  I have
>> some doubts it would be accepted as sponsored individual submission nor is
>> it appropriate for the ISE, but I could be wrong.
>>     
>
> It absolutely can not be done in the Independent Stream -- that stream
> can't do Standards Tack documents.
>   
>> I doubt this warrants its own working group, but I could be wrong about that
>> too.  So far as I’m aware the only changes needed from that document are the
>> creation of an extensions registry, some minor editorial stuff, and some
>> kind of resolution of the IESG Statement that was added to it to address the
>> collision with Sender ID (RFC4406/7).
>>     
>
> I believe this absolutely needs its own WG, and the proponents should
> work on a draft charter.  The charter should be clear that it's aiming
> to move SPF to Standards Track, that it is specifically NOT addressing
> Sender-ID, and that any merging of Sender-ID into SPF is out of scope.
>  The charter should have explanatory text about the experiment having
> been done, the results being clear, and deployment being widespread.
> The WG wants, it should say, to document the experimental results and
> shift SPF onto Standards Track.
>   
Considering past history of SPF/Sender-ID, I would advise Apps AD not to 
take it as an AD-sponsored document. So +1 for the WG, if there is 
energy to do the work.
> Hatless Barry