Re: advice on role of a WG Chair

Brian E Carpenter <brc@zurich.ibm.com> Tue, 04 July 2006 09:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fxh5z-0007F8-UO; Tue, 04 Jul 2006 05:21:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fxh5z-0007F3-CR for wgchairs@ietf.org; Tue, 04 Jul 2006 05:21:27 -0400
Received: from mtagate2.uk.ibm.com ([195.212.29.135]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fxh5x-0006QK-UG for wgchairs@ietf.org; Tue, 04 Jul 2006 05:21:27 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate2.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k649LOWh185856 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <wgchairs@ietf.org>; Tue, 4 Jul 2006 09:21:25 GMT
Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k649MoGg103352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Tue, 4 Jul 2006 10:22:50 +0100
Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k649LNGi009955 for <wgchairs@ietf.org>; Tue, 4 Jul 2006 10:21:23 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av02.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k649LNqj009942; Tue, 4 Jul 2006 10:21:23 +0100
Received: from zurich.ibm.com (sig-9-146-221-83.de.ibm.com [9.146.221.83]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA43732; Tue, 4 Jul 2006 11:21:22 +0200
Message-ID: <44AA3311.7060006@zurich.ibm.com>
Date: Tue, 04 Jul 2006 11:21:21 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <449B150F.7090803@andybierman.com> <6396E72B-CAFF-49AB-BBB0-5DF67AF547C9@cisco.com> <449C98EE.6050502@andybierman.com> <449FAD09.4060206@zurich.ibm.com> <44A01939.8060708@andybierman.com> <44A0DFF7.5040907@zurich.ibm.com> <20060627232749.GA19505@boskop.local> <44A93926.4010207@cisco.com>
In-Reply-To: <44A93926.4010207@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Working Group Chairs <wgchairs@ietf.org>
Subject: Re: advice on role of a WG Chair
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Errors-To: wgchairs-bounces@ietf.org

Eliot Lear wrote:
> Since Juergen re-raised and eveyone including myself seems to be having
> a cow about process,  let's not go overboard in either direction.  For
> instance...
> 
> Juergen Schoenwaelder wrote:
> 
>>I am waiting for a proof that the stringent documentation and process
>>rules the IETF has put in place over the last few years actually help
>>producing better documents and more running code and ultimately widely
>>deployed technology.
>>  
> 
> Seems to me a lot of the new process has been focused as much on
> improving throughput as quality.  My understanding of the PROTO process
> was that it was an effort to protect against a DDOS by working group
> chairs who were either overzealous or hadn't bothered to read their own
> drafts, thus requiring numerous rounds.  Part of that process, for
> instance, requires a draft to pass idnits, something that it has to do
> in order for the RFC Editor to take over.  A reasonable question is
> whether we believe that process has helped.  Judging by the numbers it
> seems to have, but I can't claim I understand the causal issues.

These are hard things to measure in terms of cause and effect, because
it takes several years for changes such as PROTO to fully take effect,
but I think you are correct. Similarly I believe that the availability
to the community of the IESG's DISCUSS criteria will also have such an
effect -partly by making it hard for the IESG to have ill-defined
objections to a draft, and partly by making it clearer to WGs what sort
of thing the IESG gets worried about.

I'd like to underline that these things are procedural - we haven't
made substantial changes to our process rules for year.
(Hence the question asked in draft-carpenter-newtrk-questions-00.txt,
which will be asked again in plenary next week.)

     Brian