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

John Leslie <john@jlc.net> Thu, 22 August 2013 03:02 UTC

Return-Path: <john@jlc.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 4D27E11E81AB for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.24
X-Spam-Level:
X-Spam-Status: No, score=-106.24 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 7j2FzaKPBCNt for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:02:03 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 393C711E81A6 for <ietf@ietf.org>; Wed, 21 Aug 2013 20:02:03 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9E42D33C2E; Wed, 21 Aug 2013 23:02:02 -0400 (EDT)
Date: Wed, 21 Aug 2013 23:02:02 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130822030202.GP68553@verdi>
References: <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5215123E.5080203@dcrocker.net>
User-Agent: Mutt/1.4.1i
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 22 Aug 2013 03:02:13 -0000

NB: I have read the rest of the thread; but this is what deserves a reply:

Dave Crocker <dhc@dcrocker.net> wrote:
> On 8/21/2013 11:58 AM, Pete Resnick wrote:
> 
>> AD hat squarely on my head.

   (There may have been a miscommunication here -- what particular AD
function Pete was speaking in; but to me, at least, it becomes clear
in context.)

>> On 8/21/13 1:29 PM, Dave Crocker wrote:
>>
>>> Oh.  Now I understand.
>>>
>>> You are trying to impose new requirements on the original work, many
>>> years after the IETF approved it.
>>>
>>> Thanks.  Very helpful.
>>
>> That's not an appropriate response.

   Dave has every right to disagree on that; but I quite agree with
Pete. It is decidedly not helpful, not productive, and tends towards
escalating a discussion which has no need of escalation.

>> It is certainly not helpful to me as the consensus caller.

   Dave has no right to disagree with this. We pay Pete the big bucks
to call consensus on difficult issues like this. We need to understand
it will be hard sometimes.

   I'm sure Dave has read Pete's draft on the meaning of consensus.
I'm less sure he remembered it as he responded here.

   If this is the sort of response given to somewhat-valid questions
raised about the draft being proposed, Pete will eventually have to
say there _is_ no consensus. :^(

>> And it is rude.

   Pete's opinion. (I happen to share it.)

   Consensus process works _much_ better if we respect the opinions
of others -- even when we "know" they're wrong.

> Since you've made this a formal process point,

   Pete has _not_ done this.

> I'll ask you to substantiate it carefully and also formally...

   I see no reason Pete has any obligation to do so. If he chooses
to, I ask him to not do it on this list. ("Please don't feed the
troll" comes to mind.)

> A bit of edge is warranted for such wasteful, distracting and 
> destabilizing consumption of IETF resources...

   Dave's opinion. (I happen to not share it.)

   Consensus process _also_ works better if we respect Dave's
opinion here.

   I suggest we all remember that we don't have to change others'
opinions here (were such a thing possible). We have only to bring
them to the point where they agree they can live with the result.

--
John Leslie <john@jlc.net>