Re: IETF Process Evolution

Ted Hardie <hardie@qualcomm.com> Fri, 16 September 2005 23:45 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGPta-0001lF-6D; Fri, 16 Sep 2005 19:45:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGPtY-0001lA-4q for ietf@megatron.ietf.org; Fri, 16 Sep 2005 19:45:28 -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 TAA26995 for <ietf@ietf.org>; Fri, 16 Sep 2005 19:45:24 -0400 (EDT)
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EGPyd-0007aE-Ce for ietf@ietf.org; Fri, 16 Sep 2005 19:50:44 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j8GNjCcU015955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 16 Sep 2005 16:45:13 -0700 (PDT)
Received: from [192.168.1.4] (vpn-10-50-0-124.qualcomm.com [10.50.0.124]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j8GNj97S001344; Fri, 16 Sep 2005 16:45:10 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06230907bf5107772dac@[192.168.1.4]>
In-Reply-To: <432B3918.9080303@dcrocker.net>
References: <E1EGI1e-00038I-8N@newodin.ietf.org> <p06230901bf509c2b07b4@[192.168.1.4]> <03c301c5baed$f2aa4df0$75087c0a@china.huawei.com> <p0623090abf50c3b34bc6@[192.168.1.4]> <432B3918.9080303@dcrocker.net>
Date: Fri, 16 Sep 2005 16:45:08 -0700
To: dcrocker@bbiw.net
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
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

At 2:28 PM -0700 9/16/05, Dave Crocker wrote:
>
>And since all other public development efforts for process change have frankly fallen flat, as Brian has cited, what is your basis for believing that a working group charter will somehow make yet-another public process more effective at developing a specification for change?

Possibly I'm wrong in this, but I believe that the public process works when the
community cares about the outcome.  The IASA work is done, and I believe
it is a success because enough people cared about the outcome to make it one.

As you noted a few days ago:

>Successful IETF work begins by developing support to do the development work and support to use the output of that work. The work is then done for development and deployment.
>
>The procedural simplicity and practical utility of this model tend to be vastly under-appreciated.

I believe the community will care enough about this to get it to work, and I hope
I'm right, as it will be a requirement whatever process we use to get to a new
change process.

As I said at the beginning of this thread, I believe using PESCI to scope the
work and develop support for is fine.  I'm deeply concerned, however, about it
doing the development work itself, as a process in which selected volunteers replace
the public work of those who will use the outcome.

			regards,
				Ted Hardie

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf