Re: AdminRest: IASA BCP: Executive Director

John C Klensin <john-ietf@jck.com> Sun, 28 November 2004 17:25 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 MAA29351; Sun, 28 Nov 2004 12:25:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYSsw-0007WH-2z; Sun, 28 Nov 2004 12:30:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYSlL-0005Tv-64; Sun, 28 Nov 2004 12:23:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYSk6-0005KL-D1 for ietf@megatron.ietf.org; Sun, 28 Nov 2004 12:21:50 -0500
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 MAA29107 for <ietf@ietf.org>; Sun, 28 Nov 2004 12:21:44 -0500 (EST)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYSof-0007Ls-Qb for ietf@ietf.org; Sun, 28 Nov 2004 12:26:40 -0500
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1CYSjj-000IGP-T3; Sun, 28 Nov 2004 12:21:23 -0500
Date: Sun, 28 Nov 2004 12:21:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Carl Malamud <carl@media.org>
Message-ID: <4316BD282F9D74EEBB44D55D@scan.jck.com>
In-Reply-To: <tsl7jo8qog0.fsf@cz.mit.edu>
References: <200411261836.iAQIatxP002405@bulk.resource.org> <tsl7jo8qog0.fsf@cz.mit.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: "Joel M. Halpern" <joel@stevecrocker.com>, "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: AdminRest: IASA BCP: Executive Director
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.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit


--On Friday, 26 November, 2004 16:40 -0500 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

> I think the IESG's concern here is that they, rather than the
> IAOC would like to designate who the executive director is.
> 
> The executive director is very involved in making the IESG and
> process functions run smoothly.  
> 
> It seems like significant friction would be created if the
> executive director was not someone the IESG was comfortable
> with.

Sam,

While I understand and sympathize with the concern you raise,
the whole model so far --as developed much more by the IESG and
IAB than by the community, so it presumably meets their needs --
is that we constitute an IASA and IAOC, and then let them run
the details.   If the IESG asserts the right to start appointing
(and presumably firing) particular individuals, especially
individuals who, under the current model, are contractors, we
are down the slippery slope toward a level of IESG management of
the administrative process that calls for a completely different
model.

It seems to me that it might be reasonable to expect the IAD to
seek the advice, and maybe the consent, of the IESG on an Exec
Dir appointment.  But going much further than that requires a
rather different model.

   john






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