Re: [Pesci-discuss] Growing concerns about PESCI

Brian E Carpenter <brc@zurich.ibm.com> Thu, 27 October 2005 14:16 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV8Y4-0002FB-E2; Thu, 27 Oct 2005 10:16:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV8Y3-0002F3-9o; Thu, 27 Oct 2005 10:16:07 -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 KAA02249; Thu, 27 Oct 2005 10:15:49 -0400 (EDT)
Received: from mtagate3.de.ibm.com ([195.212.29.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV8lM-0003YX-Kf; Thu, 27 Oct 2005 10:29:55 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate3.de.ibm.com (8.12.10/8.12.10) with ESMTP id j9REFr7V138954; Thu, 27 Oct 2005 14:15:53 GMT
Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j9REFq9q231768; Thu, 27 Oct 2005 16:15:52 +0200
Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av03.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j9REFqD0012102; Thu, 27 Oct 2005 16:15:52 +0200
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j9REFpoC012093; Thu, 27 Oct 2005 16:15:51 +0200
Received: from zurich.ibm.com (sig-9-145-134-138.de.ibm.com [9.145.134.138]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id QAA43820; Thu, 27 Oct 2005 16:15:48 +0200
Message-ID: <4360E100.7090206@zurich.ibm.com>
Date: Thu, 27 Oct 2005 16:15:28 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
References: <2D6A134D3C8C93F22B716D96@scan.jck.com> <435F7F3C.40403@zurich.ibm.com> <18DD6FBD0B5B0F9ABDF45C44@scan.jck.com>
In-Reply-To: <18DD6FBD0B5B0F9ABDF45C44@scan.jck.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: pesci-discuss@ietf.org, ietf@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

John C Klensin wrote:
> Brian,
> 
> Let me make this short enough to encourage easy reading when you
> wake up...
> 
> --On Wednesday, 26 October, 2005 15:06 +0200 Brian E Carpenter
> <brc@zurich.ibm.com> wrote:
> 
> 
>>And I really don't see the value of cross-posting when the
>>pesci-discuss list exists for exactly this discussion.
> 
> 
> Much of the discussion has moved to that list.  However...
> 
> To the extent to which there is a serious concern that the
> operation of PESCI and the pesci-discuss list are an abuse of
> process, the IETF list is exactly the right place to have that
> particular discussion.  

So I will respond here.

1. How can there possibly be an abuse of process when there is
no proposal on the table yet? If we succeed in forging some degree
of consensus about a set of principles, then will be the time
to apply due process to test for rough consensus in the IETF.
We could do that by forming a WG or we could do it by the non-WG
route, in full accordance with RFC 2026 process.

2. This thread, and its spin-offs on the pesci-discuss list,
neatly illustrate the exact problem I hope PESCI can resolve.
We (and that is inclusive) repeatedly fall into a very trivial
recursion on "what is the process for changing the process;
we need a process for that; what is the process for...?" My
desired output from PESCI is a set of principles to get us out
of that recursion.

What I think is more important is just that - a tight focus
on sifting and agreeing on that set of principles.

I do understand all the arguments and concerns, but we need
to get ourselves out of that recursive loop.

    Brian


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