Re: [spfbis] SPFBIS proposed charter

SM <sm@resistor.net> Fri, 02 December 2011 07:54 UTC

Return-Path: <sm@resistor.net>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F198811E809A for <spfbis@ietfa.amsl.com>; Thu, 1 Dec 2011 23:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 0yR8hWHubtHZ for <spfbis@ietfa.amsl.com>; Thu, 1 Dec 2011 23:54:56 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4493811E8094 for <spfbis@ietf.org>; Thu, 1 Dec 2011 23:54:56 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id pB27snqS009890; Thu, 1 Dec 2011 23:54:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1322812495; bh=S3RQSCPnub8reFAbUKI7JWeGP5v1IwZM5KTSiB8MPx4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=nN+ylrdxOxC0ZuR2jFM9DylFuAisOUhAeXO8kJ2niisWTwl5kYBVSq2icQ8kSdgqG 4UVlDyjgt2Knoxs7zGr4Ij9oUKpbyfixtaiEuqxs5Rh6WHtzIR2huiRNU8/P+0E7u7 sIki3dOZHj5j5kGs+ywdTIDQU0K0WVErQoJZH/Po=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1322812495; bh=S3RQSCPnub8reFAbUKI7JWeGP5v1IwZM5KTSiB8MPx4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=NY8TXRHknmfdTs2/KMtEpXP0/tCrg0nOs4Xx1THvmgNtCM1Hfi1xVEJz8n6MIN9TR /G3+SGg0iXXG9cCiVkOGy0Fpj444zKsQaB7ULw0IVr/wIjzUIXaxjTDzP7arcuvOkO sAW5ZxLRxH4TEKw4DiS2Qh4MPQtr817D7EYZ3lyg=
Message-Id: <6.2.5.6.2.20111201231730.09055288@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Dec 2011 23:54:32 -0800
To: Paul Midgen <pmidge@microsoft.com>
From: SM <sm@resistor.net>
In-Reply-To: <7F7F36E50398F84DBAF25C9D51732F1E2042B0E4@TK5EX14MBXC202.re dmond.corp.microsoft.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C152FD@EXCH-C2.corp.cloudmark.com> <F5833273385BB34F99288B3648C4F06F19C6C15302@EXCH-C2.corp.cloudmark.com> <6.2.5.6.2.20111130134620.0caeabd0@resistor.net> <F5833273385BB34F99288B3648C4F06F19C6C15309@EXCH-C2.corp.cloudmark.com> <6.2.5.6.2.20111201211727.0a155128@resistor.net> <F5833273385BB34F99288B3648C4F06F19C6C1539D@EXCH-C2.corp.cloudmark.com> <6.2.5.6.2.20111201223320.09054ff8@resistor.net> <7F7F36E50398F84DBAF25C9D51732F1E2042B0E4@TK5EX14MBXC202.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: spfbis@ietf.org
Subject: Re: [spfbis] SPFBIS proposed charter
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 07:54:57 -0000

Hi Paul,
At 23:03 01-12-2011, Paul Midgen wrote:
>I'm still relatively inexperienced in the standards process, so keep 
>that in mind when reading my comments.

If my comments are unclear, please let me know and I'll elaborate.

>One of SPFbis' efforts will be to publish data detailing current 
>operational characteristics of SPF & SenderID (the document Dave 
>Crocker mentioned), and said data will inform SPFbis. As has been 
>mentioned, it's not terribly interesting (to me, anyway) what 
>happens with RFCs 4406 & 4407.

draft-kitterman-4408bis will obsolete RFC 4408 and according to the 
proposed charter will be published as a Proposed Standard.

>Having now given draft-mehnle-spf-scope a first read, my hope that 
>what it essentially proposes (inclusion of some number of RFC5322 
>headers as authenticatable identities)

Yes.

>  finds its way into SPFbis, and that doing so is supported by 
> operational data. I've seen this to be true anecdotally, but want 
> it out there in published form with data from multiple receivers, 
> senders, etc. included in the analysis.

I prefer not to comment on this during the chartering discussion as 
it might end up being controversial.

At 23:05 01-12-2011, Paul Midgen wrote:
>Murray and I have had some discussion on this prior to starting 
>SPFbis, and the work is already in progress - though my contribution 
>to it won't be ready for some months, since I'm constrained by my 
>current ability to gather all the data I want.
>
>So - before we start editing and circulating documents, we should 
>first have a discussion on what all our thoughts/expectations are.

Good idea.  I am ok with whatever the consensus is for the "conclusions" draft.

This mailing list has been quiet which is unusual for a fora where 
SPF and Sender-ID is mentioned.  It's better to have the 
above-mentioned discussion after the working group is chartered as 
there will be a WG chair to deal with the controversies.

Regards,
-sm