Re: [nfsv4] rough consensus

Nicolas Williams <Nicolas.Williams@oracle.com> Thu, 30 September 2010 22:33 UTC

Return-Path: <Nicolas.Williams@oracle.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDE823A6CCB for <nfsv4@core3.amsl.com>; Thu, 30 Sep 2010 15:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIc5Sr39SL4V for <nfsv4@core3.amsl.com>; Thu, 30 Sep 2010 15:32:56 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 2A7723A6C7E for <nfsv4@ietf.org>; Thu, 30 Sep 2010 15:32:52 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o8UMXZ4B008169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Sep 2010 22:33:37 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o8U9vu5N009285; Thu, 30 Sep 2010 22:33:34 GMT
Received: from abhmt006.oracle.com by acsmt355.oracle.com with ESMTP id 652136791285885987; Thu, 30 Sep 2010 15:33:07 -0700
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 30 Sep 2010 15:33:07 -0700
Date: Thu, 30 Sep 2010 17:33:01 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: david.black@emc.com
Message-ID: <20100930223300.GG9501@oracle.com>
References: <E043D9D8EE3B5743B8B174A814FD584F09C3F21A@TK5EX14MBXC126.redmond.corp.microsoft.com> <12DF0AF06D38492FB34731B462348640@23FX1C1> <BF3BB6D12298F54B89C8DCC1E4073D80027650EE@CORPUSMX50A.corp.emc.com> <89B1192DD67049C284456E5A1D9C3EF4@23FX1C1> <BF3BB6D12298F54B89C8DCC1E4073D8002765140@CORPUSMX50A.corp.emc.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03D1B61426@MX14A.corp.emc.com> <BF3BB6D12298F54B89C8DCC1E4073D8002765321@CORPUSMX50A.corp.emc.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03D1B61614@MX14A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E03D1B61614@MX14A.corp.emc.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] rough consensus
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2010 22:33:32 -0000

On Thu, Sep 30, 2010 at 06:11:26PM -0400, david.black@emc.com wrote:
> [...]
> 
> I concur on that fundamental issue - IETF is absolutely supposed to
> work in the former fashion (WG as partner in the process).  I had read
> Spencer's message as strongly discouraging consensus calls by those
> who are not WG chairs, which (as a WG chair myself) I believe is
> appropriate.

+1 David Black's comments.

I believe it is appropriate for a participant to request a consensus
call.  I believe it's also appropriate for a participant to voice their
opinion as to what the consensus is.  Statements such as "<WG chair
name>, I believe you'll agree with me that there is consensus on this
question" are fair enough, though of course such statements are not
authoritative, and the chair may well disagree with them.

Even statements such as "there is rough consensus for X" from non-chairs
are allowable -- they just aren't authoritative, and therefore not
useful.  It's much better to qualify such statements accordingly, and
it's even better to request a formal determination of consensus.

The relevant I-D's authors would do well to submit a new version, then
request whatever procedure is appropriate.  E.g., if it's not a work
item and the authors wish it were, then ask for a consensus call
regarding that, or, if the authors think the I-D is ready, they could
ask for a WG Last Call, and so on.

As far as I can see, there's nothing to see here.

Cheers,

Nico
--