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

Harald Alvestrand <harald@alvestrand.no> Fri, 28 April 2006 13:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZT0F-0005Iy-4X; Fri, 28 Apr 2006 09:27:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZT0D-0005It-15 for ietf@ietf.org; Fri, 28 Apr 2006 09:27:21 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZT0C-0001sj-HW for ietf@ietf.org; Fri, 28 Apr 2006 09:27:21 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 107FB259700; Fri, 28 Apr 2006 15:26:51 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18666-04; Fri, 28 Apr 2006 15:26:45 +0200 (CEST)
Received: from [127.0.0.1] (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id ABB3D2596FA; Fri, 28 Apr 2006 15:26:45 +0200 (CEST)
Message-ID: <44521831.7080806@alvestrand.no>
Date: Fri, 28 Apr 2006 15:27:13 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <4451FF45.1070404@zurich.ibm.com>
In-Reply-To: <4451FF45.1070404@zurich.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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

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