Re: [Pesci-discuss] Finding and nurturing the bright sparks of genius

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 26 October 2005 13:03 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkwZ-0003XL-Vk; Wed, 26 Oct 2005 09:03:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkwZ-0003WK-2B for pesci-discuss@megatron.ietf.org; Wed, 26 Oct 2005 09:03:51 -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 JAA17957 for <pesci-discuss@ietf.org>; Wed, 26 Oct 2005 09:03:36 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUl9f-0000nH-Ju for pesci-discuss@ietf.org; Wed, 26 Oct 2005 09:17:27 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id F1B9D2596BD; Wed, 26 Oct 2005 15:02:57 +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 17014-10; Wed, 26 Oct 2005 15:02:54 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1536C258043; Wed, 26 Oct 2005 15:02:52 +0200 (CEST)
Date: Wed, 26 Oct 2005 05:52:05 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Elwyn Davies <elwynd@dial.pipex.com>, pesci-discuss@ietf.org
Subject: Re: [Pesci-discuss] Finding and nurturing the bright sparks of genius
Message-ID: <F2C57C27B6C69254E554E419@B50854F0A9192E8EC6CDA126>
In-Reply-To: <435F63E7.1050705@dial.pipex.com>
References: <435F63E7.1050705@dial.pipex.com>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc:
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>
Content-Type: multipart/mixed; boundary="===============0505996478=="
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

Elwyn,

one further thought.....

--On 26. oktober 2005 12:09 +0100 Elwyn Davies <elwynd@dial.pipex.com> 
wrote:

> If we agree that there is some sort of  problem, it seems to me that
> almost any means is legitimate as a way to find the kernel of a solution.
> If the current draft does revisit the ground covered by 'problem' maybe
> it will trigger the Eureka moment in somebody for some part of a
> perceived problem and they (and maybe some of their colleagues) can come
> up with a strawman that we can discuss.  Until we have a strawman, the
> discussion is likely to remain unfocussed and procedural rather than
> solutional as it has done for the last couple of years

we have, in the years since Yokohama, as Dave's fond of marking time, had 
literally dozens of strawmen for how the process should be changed - 
including mandatory deadlines on WGs, constitutional limits on WGs per 
area, term limits on ADs, RFCs in HTML, I-Ds in XML, creating public IESG 
ballots, taking document review away from the IESG, splitting up the IESG 
into functional units, instituting early review, instituting late review, 
instituting cross-area review, changing IESG voting rules, appointing WG 
secretaries, public document tracking, making WG chairs shepherd 
documents... just to name a few.

Some of these have been adopted, most have not. And of the set not adopted, 
one common thread for many is that we do not know *how to make that change*.

The "just do it" department has usually come up against the principle 
described in the PESCI document as

>    G5.  Avoid changes that would require unrealistic resources or
>         behaviours.

PESCI itself is a short-term event. Its legitimacy is not even interesting 
to me - it needs none, if its output is right.

My most burning question is whether section 6 of the PESCI document is a 
realistic and acceptable way forward to get the process of getting 
important changes done running - or whether the proposal needs further 
elaboration or change in order to answer that question at all.
And to have any information about that, someone needs to comment on *that*.

So far, I don't think many have.

                      Harald



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