Re: IETF Process Evolution

Dave Crocker <dhc2@dcrocker.net> Fri, 16 September 2005 21:29 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGNlj-0004JA-Vo; Fri, 16 Sep 2005 17:29:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGNlh-0004J2-A4 for ietf@megatron.ietf.org; Fri, 16 Sep 2005 17:29:13 -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 RAA20540 for <ietf@ietf.org>; Fri, 16 Sep 2005 17:29:10 -0400 (EDT)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EGNql-0004iV-GP for ietf@ietf.org; Fri, 16 Sep 2005 17:34:28 -0400
Received: from [192.168.0.2] (adsl-71-131-50-87.dsl.sntc01.pacbell.net [71.131.50.87]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id j8GLTgJF018651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Sep 2005 14:29:43 -0700
Message-ID: <432B3918.9080303@dcrocker.net>
Date: Fri, 16 Sep 2005 14:28:56 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: Ted Hardie <hardie@qualcomm.com>
References: <E1EGI1e-00038I-8N@newodin.ietf.org> <p06230901bf509c2b07b4@[192.168.1.4]> <03c301c5baed$f2aa4df0$75087c0a@china.huawei.com> <p0623090abf50c3b34bc6@[192.168.1.4]>
In-Reply-To: <p0623090abf50c3b34bc6@[192.168.1.4]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: IETF Process Evolution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
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


> 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.

Ted,

Groups like nomcom and ipr have not had a multi-year crisis with a history of 
extensive activity and little measurable improvement to show for it. (How long 
ago was Yokohama?)

So, Ted, how long should be allocated for this process to define a charter to 
define a working group that will define process changes?

How long to get community acceptance for it?

How long to get a resulting working group to produce something useful?

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?

Design teams design solutions, not plans for solutions or charters for working 
groups.  If the design team knows enough about its topic -- especially when 
the topic is complex and not all that well understood -- it is usually a far 
more effective vehicle for solution specification than is the working group 
framework.

d/

-- 

  Dave Crocker
  Brandenburg InternetWorking
  +1.408.246.8253
  dcrocker  a t ...
  WE'VE MOVED to:  www.bbiw.net

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