Declarers of consensus (Re: [Pesci-discuss] My Notes)

Harald Tveit Alvestrand <harald@alvestrand.no> Thu, 20 October 2005 08:07 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVS4-0005ts-Mf; Thu, 20 Oct 2005 04:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVS3-0005su-HZ for pesci-discuss@megatron.ietf.org; Thu, 20 Oct 2005 04:07:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23475 for <pesci-discuss@ietf.org>; Thu, 20 Oct 2005 04:06:53 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESVdu-00070y-EA for pesci-discuss@ietf.org; Thu, 20 Oct 2005 04:19:21 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 74EF52596AF; Thu, 20 Oct 2005 10:06:14 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31366-05; Thu, 20 Oct 2005 10:06:10 +0200 (CEST)
Received: from [192.168.1.160] (163.80-203-220.nextgentel.com [80.203.220.163]) by eikenes.alvestrand.no (Postfix) with ESMTP id AA2D2258093; Thu, 20 Oct 2005 10:06:10 +0200 (CEST)
Date: Thu, 20 Oct 2005 10:07:24 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Scott W Brim <swb@employees.org>, Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Declarers of consensus (Re: [Pesci-discuss] My Notes)
Message-ID: <4129B03F015A4F572E51325A@svartdal.hjemme.alvestrand.no>
In-Reply-To: <4356CD15.4060006@employees.org>
References: <43535DFB.2040909@zurich.ibm.com> <0bca01c5d4e0$e3341010$0500a8c0@china.huawei.com> <4356CD15.4060006@employees.org>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: pesci-discuss@ietf.org
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org


--On onsdag, oktober 19, 2005 18:47:49 -0400 Scott W Brim 
<swb@employees.org> wrote:

>> 6.1.  Change Process Proposal
>>
>>
>> SD: It bothers me that this document handwaves approval of process
>> change ("the IESG (and ISOC Board of Trustees) will respect that
>> consensus and approve it") - who actually DECLARES the consensus that
>> the IESG and ISOC BoT then respect? Note that I haven't got a better
>> answer, but the default now looks like "Brian declares consensus (or
>> lack thereof) based on [fill in the blank here], and if no one
>> successfully appeals to IAB/ISOC BoT, we know where we're going" - and
>> if this isn't the default, what is?
>>
>>   The teams should function with an open discussion list, in the same
>>   way that the PESCI committee has done.  The result of the committee
>>   should be tested against the IETF consensus in the normal fashion; we
>>   believe that if there is clear IETF consensus that the proposal makes
>>   sense, the IESG (and the ISOC Board of Trustees) will respect that
>>   consensus and approve of it.
>
> I'm stepping back from this one because I'm out of time.  I look
> forward to others' opinions.

PESCI stepped back from this one too.......

I think the answer's likely to be "the team discusses its result openly in 
the IETF, using process X, and some person designated by the IETF chair 
declares that he has concluded that the IETF has consensus".

This follows a model of the IETF as "WG", and the team analogous to the 
"design team". Still unclear whether the person declaring IETF consensus 
has to be part of the team developing the proposal or not (practice for 
design teams varies).

That declaration of consensus would then be evaluated by the bodies having 
to approve the document (including the IESG and the ISOC BoT), and my hope 
is that it's going to be "pretty obvious" - because the spectacle of trying 
for process change based on a declaration of consensus that can be 
questioned to death in detail may cause us all to prefer the 51% 
dictatorship of voting :-(

Of course, one danger is that the only changes we're able to make is the 
obvious ones..... but that seems a danger in all efforts to change the IETF.

                       Harald




_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss