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

Dave CROCKER <dhc@dcrocker.net> Wed, 10 August 2011 00:11 UTC

Return-Path: <dhc@dcrocker.net>
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 4582D21F8C29 for <apps-discuss@ietfa.amsl.com>; Tue, 9 Aug 2011 17:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wcGaljf6ugDa for <apps-discuss@ietfa.amsl.com>; Tue, 9 Aug 2011 17:11:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 95F7121F8C1D for <apps-discuss@ietf.org>; Tue, 9 Aug 2011 17:11:07 -0700 (PDT)
Received: from [192.168.1.3] (cpe-76-93-128-131.san.res.rr.com [76.93.128.131]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7A0BUGU006114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2011 17:11:37 -0700
Message-ID: <4E41CCB2.9040402@dcrocker.net>
Date: Tue, 09 Aug 2011 17:11:30 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
References: <AcxV+CxT9WxP2wTLTNWpQ3LXOor+nw==> <F5833273385BB34F99288B3648C4F06F13512DF606@EXCH-C2.corp.cloudmark.com> <CAC4RtVCncUmdM+g8c+tTBGMnXHtL5+5hGwNF7+n14sDbBst8WQ@mail.gmail.com> <4E4112B4.7000905@tana.it> <F5833273385BB34F99288B3648C4F06F13512DF642@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF642@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Aug 2011 17:11:37 -0700 (PDT)
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
Reply-To: dcrocker@bbiw.net
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: Wed, 10 Aug 2011 00:11:08 -0000

On 8/9/2011 10:19 AM, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Alessandro Vesely
>> Sent: Tuesday, August 09, 2011 3:58 AM
>> To: apps-discuss@ietf.org
>> Subject: Re: [apps-discuss] Updating the status of SPF
>>
>> +1, this is a Good Thing to do!
>
> Does that mean you (all) are volunteering to review stuff and comment, and possibly co-chair?


I'll offer to co-chair.

There's some history to this effort, going back to MAAWG, where I was one of 3 
folk raising their hands to pursue this.  Somehow things wandered through a 
circuitous route and I got decoupled from it.

Historically and vocally, I'm not a fan of SPF.  However I am /always/ a fan of 
good documentation for existing practice and I don't believe in using 
documentation processes to exercise religious preference.  An effort to produce 
tight, pragmatic SPF documentation should be accurate and usable.

I offered to assist the effort both to navigate the politics and to press for 
clean workable documentation.

I'll suggest, however, that there is good reason for concern about any 
expectation that this will be a simple and/or easy effort.  It will be wonderful 
for that to happen, but SPF invites the contrary.

A few tidbits as examples:

   *  It uses TXT without an underscore, thereby inviting the classic scaling 
argument against using TXT.  This invites pushback from the DNS folk.

   *  It is based on an implied semantic of SMTP Mail From that correlates with 
actual use, but not formal semantics of the field.  This invites pushback from 
(some) email folk.

   *  It is used for anti-abuse.  This invites pushback from anyone who thinks 
they are an expert in anti-abuse and has any sort of agenda, releant or not, and 
we've already seem plenty of that over the last 7-9 years.

While this probably does need a working group, it most definitely needs a 
collaborative, core design team that shares a coherent and constrained set of 
goals for the effort and that can work together.

d/



-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net