Re: admin director (was The other parts of the report..)

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 15 September 2004 10:07 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18641; Wed, 15 Sep 2004 06:07:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7Wlv-00085i-1Y; Wed, 15 Sep 2004 06:12:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7WfK-0002IW-Qa; Wed, 15 Sep 2004 06:05:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7WbX-0001v3-Qg for ietf@megatron.ietf.org; Wed, 15 Sep 2004 06:01:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18404 for <ietf@ietf.org>; Wed, 15 Sep 2004 06:01:33 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7Wgc-00081a-KC for ietf@ietf.org; Wed, 15 Sep 2004 06:06:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 24DB061BD7; Wed, 15 Sep 2004 12:01:03 +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 07873-07; Wed, 15 Sep 2004 12:01:01 +0200 (CEST)
Received: from [192.168.1.4] (145.80-202-211.nextgentel.com [80.202.211.145]) by eikenes.alvestrand.no (Postfix) with ESMTP id 579BA61AD5; Wed, 15 Sep 2004 12:01:01 +0200 (CEST)
Date: Wed, 15 Sep 2004 12:01:02 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Brian E Carpenter <brc@zurich.ibm.com>, John C Klensin <john-ietf@jck.com>
Message-ID: <8024C6E799E9847B80E1B858@askvoll.hjemme.alvestrand.no>
In-Reply-To: <414808C8.6050806@zurich.ibm.com>
References: <20040910124953.AF97886077@newdev.harvard.edu> <9EF0BCF3DC95C174563EA12E@scan.jck.com> <4145B4CD.3070601@zurich.ibm.com> <58B1E47C9B1B84DEEA9717B9@scan.jck.com> <414808C8.6050806@zurich.ibm.com>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: admin director (was The other parts of the report..)
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
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Brian,

your timeline looks very deliberate and formally correct.
However, I worry about the ability of the IETF to work constructively while 
knowing that its future is still in flux for that long.

So I put some dates in.

--On onsdag, september 15, 2004 11:18:00 +0200 Brian E Carpenter 
<brc@zurich.ibm.com> wrote:

> John,
>
> I fully agree. To me the only sequence of events that makes sense is
>
> 1. Agree on the job description. (But it needs to drafted by a small
> group first.)

September/October 2004. We have a draft job description in appendix E of 
the report, and very few (no?) specific comments on that draft.

> 2. Ask ISOC to fund a position for 1 year, and hire someone. (But
> the IETF leadership has to be intimately involved in the
> hiring process.)

Budget approval: October/November. Not a problem, I think.
If search takes 3 months: February 2005 for the hire.

> 3. Have the new person develop a budget model and the RFP. (But
> the IETF community gets to review the draft RFP.)

If the person does not know the IETF intimately: May 2005 (3 months).
Considerably shorter if person accepts previous work - but that runs into 
almost the same issues as "RFP sent out before hire".

Contracts: Fall 2005.

> 4. Worry about whether to create a separate legal entity later.
>

2006?






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