Re: IETF Process Evolution
"C. M. Heard" <heard@pobox.com> Fri, 16 September 2005 21:53 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGO9M-0001JU-Q4; Fri, 16 Sep 2005 17:53:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGO9L-0001JO-Hu for ietf@megatron.ietf.org; Fri, 16 Sep 2005 17:53:39 -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 RAA21428 for <ietf@ietf.org>; Fri, 16 Sep 2005 17:53:36 -0400 (EDT)
Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EGOEO-0005DB-Jm for ietf@ietf.org; Fri, 16 Sep 2005 17:58:54 -0400
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j8GLrKBT000624 for <ietf@ietf.org>; Fri, 16 Sep 2005 14:53:20 -0700
Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j8GLr8xF031491; Fri, 16 Sep 2005 14:53:08 -0700
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id j8GLr7Ui031488; Fri, 16 Sep 2005 14:53:08 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Fri, 16 Sep 2005 14:53:07 -0700
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: IETF <ietf@ietf.org>
In-Reply-To: <E1EGI1e-00038I-8N@newodin.ietf.org> <p06230901bf509c2b07b4@[192.168.1.4]> <03c301c5baed$f2aa4df0$75087c0a@china.huawei.com> <p0623090abf50c3b34bc6@[192.168.1.4]>
Message-ID: <Pine.LNX.4.10.10509161428520.23603-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: Re: IETF Process Evolution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Fri, 16 Sep 2005, Ted Hardie wrote: > At 1:39 PM -0500 9/16/05, Spencer Dawkins wrote: > > While it seems plausible that we could use the same mechanism > > for protocol design and for process evolution, my understanding > > of the Problem working group's efforts and the subsequent > > newtrk/icar/proto/mpowr (and yes, there were others) efforts is > > that this approach simply does not work. > > Spencer, > "simply does not work" is good rhetoric, but it doesn't > fit all the facts. Groups like NomCom and IPR have taken on > tasks and done them, with community discussion of their charters > and with community discussion as their documents went through > the process. They are process change groups, and they work. >From my perspective I would have to say that the preponderance of the evidence supports Spencer's position. My reaction to your initial response to Brian's message proposing yet another WG was "oh, and it will be as successful as newtrk". Of course I could have added icar or sirs or the others that Spencer mentioned. And it's funny that you metion IPR as a success ... it seems to me that a lot of energy was spent to get very little, and in may ways it was a step backward (e.g., non-IETF folks now have to go to document authors to get permission to use a MIB etract or program fragment). For sure, the IPR effort has resulted in a delay of at least 18 months (with the clock still ticking) in getting the MIB review guidelines doc published (and I suspect, but cannot prove, that it is largely responsible for the long delay in getting rfc2223bis published). Even granting that nomcom has been a success -- I don't know the evidence in that case one way or another -- I'd have to say that the overall record for process change WGs has been very poor. In any case I would like to go on record as strongly supporting Brian's initiative. Given the lack of progress in newtrk and the like I think it's the only hope of moving forward. Mike Heard _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: IETF Process Evolution Ted Hardie
- Re: IETF Process Evolution Spencer Dawkins
- Re: IETF Process Evolution Ted Hardie
- Re: IETF Process Evolution Dave Crocker
- Re: IETF Process Evolution C. M. Heard
- Re: IETF Process Evolution Ted Hardie
- Re: IETF Process Evolution Joel M. Halpern
- Re: IETF Process Evolution Spencer Dawkins
- Re: IETF Process Evolution John C Klensin
- Re: IETF Process Evolution Pekka Savola
- Re: IETF Process Evolution Ted Hardie
- Re: IETF Process Evolution JFC (Jefsey) Morfin
- Re: IETF Process Evolution Brian E Carpenter
- Re: IETF Process Evolution Brian E Carpenter
- Re: IETF Process Evolution Spencer Dawkins
- Re: IETF Process Evolution Leslie Daigle
- Re: IETF Process Evolution Harald Tveit Alvestrand
- Re: IETF Process Evolution Brian E Carpenter