Re: Almost certainly (was Re: [Pesci-discuss] Finding and nurturing thebright sparks of genius)

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 27 October 2005 09:36 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV4Az-00073o-1G; Thu, 27 Oct 2005 05:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV4Ax-000726-0H for pesci-discuss@megatron.ietf.org; Thu, 27 Oct 2005 05:35:59 -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 FAA18206 for <pesci-discuss@ietf.org>; Thu, 27 Oct 2005 05:35:43 -0400 (EDT)
Received: from blaster.systems.pipex.net ([62.241.163.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV4OG-0004LO-58 for pesci-discuss@ietf.org; Thu, 27 Oct 2005 05:49:46 -0400
Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by blaster.systems.pipex.net (Postfix) with ESMTP id 57F63E0001C6 for <pesci-discuss@ietf.org>; Thu, 27 Oct 2005 10:35:39 +0100 (BST)
Received: from Puppy ([217.158.132.145] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 27 Oct 2005 10:29:18 +0100
Message-ID: <04e601c5dad9$55e88f70$de849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pesci-discuss@ietf.org>
References: <435F63E7.1050705@dial.pipex.com> <0b7d01c5da9d$538e6a10$20a623c0@china.huawei.com>
Subject: Re: Almost certainly (was Re: [Pesci-discuss] Finding and nurturing thebright sparks of genius)
Date: Thu, 27 Oct 2005 10:31:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 27 Oct 2005 09:29:19.0445 (UTC) FILETIME=[E8436850:01C5DAD8]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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

Hi Spencer,

It does depend on what we mean by "principle".

> The work that the PESCI team has done is good work, but we still don't
know
> what the principles ARE - for my definition of "principle" - something
that
> cannot change without the IETF not being the IETF, but turning into
> something else.

We did recognise that there are two grades of principle (maybe loosely
categorised as "immutable" and "guiding").
Would it have helped (would it help in future work) to separate these out,
or would that simply introduce another area for debate?

My personal view is that a lot of previous attempts at process change have
foundered on discussions of the form
- "but if we make that change then we will no longer do xyz"
- "it doesn't matter if we no longer do xyz"
- "oh yes it does"
- "oh no it doesn't"

> My suggestion, based on not a lot of sleep or thought, is that the BOF
focus
> on getting community feedback on what the principles are, and the list
of
> 30-something is a reasonable starting point to winnow from.

Winnowing is fine by me.

We also found, as we put the draft together, that expressing principles
was hard. Repeatedly we found that what we wrote was a consequence of a
principle and not the actual principle. So feedback and discussion of the
list is most welcome.

> I can say this on this list, on the IETF list, at the BOF, or at the
> plenary, but whatever else we need between Vancouver and Dallas for
process
> evolution to move forward, we need to know those principles.
>
> The alternative is that we evolve the IETF process in a way that the
> community will not follow, and that would be very unfortunate.

Thanks,
Adrian


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