Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard

Dave Crocker <dhc@dcrocker.net> Thu, 29 August 2013 19:29 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FAC11E8155 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:29:10 -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 GLNqn8lbksgH for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:29:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5B06311E814C for <ietf@ietf.org>; Thu, 29 Aug 2013 12:29:06 -0700 (PDT)
Received: from [172.29.109.57] (wsip-184-191-162-57.sd.sd.cox.net [184.191.162.57]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7TJT2dZ005550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 29 Aug 2013 12:29:06 -0700
Message-ID: <521FA0F9.6000107@dcrocker.net>
Date: Thu, 29 Aug 2013 12:28:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net> <33BAD063A63D81764705AC33@JcK-HP8200.jck.com>
In-Reply-To: <33BAD063A63D81764705AC33@JcK-HP8200.jck.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.66]); Thu, 29 Aug 2013 12:29:06 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 19:29:11 -0000

On 8/29/2013 9:31 AM, John C Klensin wrote:
> I may be violating my promise to myself to stay out of
> SPF-specific issues,


Probably not, since your note has little to do with the realities of the 
SPFbis draft, which is a chartered working group product.  You might 
want to review its charter:

      http://datatracker.ietf.org/wg/spfbis/charter/

Note the specified goal of standards track and the /very/ severe 
constraints on work to be done.  Please remember that this is a charter 
that was approved by the IESG.  The working group produced was it was 
chartered to produce, for the purpose that was chartered.

More broadly, you (and others) might want to review that actual criteria 
the IETF has specified for Proposed in RFC2026.  Most of us like to cite 
all manner of personal criteria we consider important.  Though 
appealing, none of them is assigned formal status by the IETF, with 
respect to the Proposed Standards label; I believe in fact that there is 
nothing that we can point to, for such other criteria, represents IETF 
consensus for them.  The claim that we can't really document our 
criteria mostly means that we think it's ok to be subjective and 
whimsical.

Also for the broader topic, you also might want to reevaluate much of 
what your note does say, in light of the realities of Individual 
Submission (on the IETF track) which essentially never conforms to the 
criteria and concerns you seem to be asserting.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net