Re: Possible General Area MiniBOF 1: IESG structure and charter

Brian E Carpenter <brc@zurich.ibm.com> Fri, 28 April 2006 15:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZUV7-0005ae-6C; Fri, 28 Apr 2006 11:03:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZUV5-0005Wy-2Q for ietf@ietf.org; Fri, 28 Apr 2006 11:03:19 -0400
Received: from mtagate3.uk.ibm.com ([195.212.29.136]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZUV4-00070K-JE for ietf@ietf.org; Fri, 28 Apr 2006 11:03:19 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate3.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k3SF3HH4030084 for <ietf@ietf.org>; Fri, 28 Apr 2006 16:03:18 +0100
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k3SF44H6058992 for <ietf@ietf.org>; Fri, 28 Apr 2006 16:04:04 +0100
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id k3SF3H1s024128 for <ietf@ietf.org>; Fri, 28 Apr 2006 16:03:17 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id k3SF3HMS024116; Fri, 28 Apr 2006 16:03:17 +0100
Received: from zurich.ibm.com (sig-9-145-252-130.de.ibm.com [9.145.252.130]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA41436; Fri, 28 Apr 2006 17:03:16 +0200
Message-ID: <44522EB4.9050904@zurich.ibm.com>
Date: Fri, 28 Apr 2006 17:03:16 +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: Harald Alvestrand <harald@alvestrand.no>
References: <4451FF45.1070404@zurich.ibm.com> <44521831.7080806@alvestrand.no>
In-Reply-To: <44521831.7080806@alvestrand.no>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: IETF discussion list <ietf@ietf.org>
Subject: Re: Possible General Area MiniBOF 1: IESG structure and charter
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>
Errors-To: ietf-bounces@ietf.org

Harald,

I believe (speaking personally) that the analysis described below
would take enormous effort and would probably take a couple of years.
And despite the description, it isn't really focussed on the IESG -
the IESG's role is actually defined more or less automatically
by all the surrounding entities, procedures, and external forces.

I think we need to take smaller bites. My ambition is much less, indeed.

Of course, anyone who thinks they can identify energetic
resources to tackle what you cite below is free to propose
a BOF (but it clearly can't be a mini-BOF within another
meeting, for such a big topic.)

    Brian

Harald Alvestrand wrote:
> Brian,
> 
> before asking for volunteers, you should state clearly whether you want 
> people who will:
> 
> - DOCUMENT the EXISTING way the IESG works, and seek approval for that
> - PROPOSE a NEW way the IESG can work, that fits the needs of the 
> community better
> 
> The last one is what draft-davies-pesci-next-steps-00 was trying to 
> suggest when it said:
> 
>   The most important single management role in the IETF at the moment
>   is that of the IESG, including the role of IETF Chair.  This should
>   therefore also receive the most scrutiny.  It's unreasonable to ask
>   people to grade their own performance, or to attempt to perform a
>   role at full speed while having to review how it could be done
>   otherwise.  Therefore, a review of the roles the IESG has should be
>   rooted outside the IESG - while asking current and former IESG
>   members for information and advice at every opportunity.
> 
>   This review should include:
> 
>   o  Creating a list of the tasks that currently gate on the IESG
>   o  Identifying any additional related tasks that might be appropriate
>      to improve efficiency and effectiveness
>   o  Making proposals for discarding or restructuring the existing
>      tasks in combination with the new tasks
>   o  Making a proposal for grouping those tasks into separate task
>      groups that can be assigned to different bodies at need.
>   o  Developing a proposal for how the standards development work of
>      the IETF should be partitioned to provide optimum efficiency while
>      allowing the IETF to take on all appropriate work.
>   o  Developing a suggestion for an initial set of bodies for handling
>      those tasks in the new work partitioning scheme, including, if
>      appropriate, a restructuring of the IESG.
>   o  Describing the process by which the set of bodies gets modified.
>   o  Describing how members of the proposed bodies get selected,
>      replaced, and (if needed) removed.
>   o  Proposing a structure for the documentation of the IETF process
>      that would result from their recommendations
> 
> Your words suggest a far more timid approach.
> 
>                     Harald
> 
> 
> 
> Brian E Carpenter wrote:
> 
>> People willing to work actively (i.e draft or
>> and edit) a document on this topic are
>> invited to contact me immediately. The objective
>> is to plan a mini-BOF during the General Area open
>> meeting at IETF 66. Without committed volunteers
>> in the community, this work will not happen.
>>
>> The IESG charter (RFC 3710) was intentionally published
>> as an Informational RFC to fill a known gap, without the
>> overhead and formality of a BCP. It may now be appropriate
>> to refine and adapt it, based on experience and changes
>> since RFC 3710 was published. At minimum, the creation
>> of IASA requires makes some updates necessary.
>> (Note that draft-carpenter-ietf-chair-tasks contains
>> some relevant comments.)
>>
>> RFC 3710 was produced by the IESG itself. I would certainly
>> want IESG members to be involved in any revision, but
>> it is important that members of the community also
>> take an active role, to ensure that the result meets
>> community expectations as well as practical reality.
>>
>>   Brian Carpenter
>>   General Area Director
>>
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>>
> 

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