Re: AdminRest: IASA BCP: Executive Director

Carl Malamud <carl@media.org> Fri, 26 November 2004 22:36 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 RAA29671; Fri, 26 Nov 2004 17:36:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXolo-0001ud-Uz; Fri, 26 Nov 2004 17:40:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXodC-0001Ue-Sw; Fri, 26 Nov 2004 17:31:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXocF-0001Ei-Cu for ietf@megatron.ietf.org; Fri, 26 Nov 2004 17:30:59 -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 RAA29262 for <ietf@ietf.org>; Fri, 26 Nov 2004 17:30:57 -0500 (EST)
Received: from bulk.resource.org ([192.101.98.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXoga-0001e5-U2 for ietf@ietf.org; Fri, 26 Nov 2004 17:35:30 -0500
Received: from bulk.resource.org (localhost.resource.org [127.0.0.1]) by bulk.resource.org (8.12.2/8.12.2) with ESMTP id iAQMUOrF025524; Fri, 26 Nov 2004 14:30:24 -0800 (PST)
Received: (from carl@localhost) by bulk.resource.org (8.12.2/8.12.2/Submit) id iAQMUOEv025523; Fri, 26 Nov 2004 14:30:24 -0800 (PST)
From: Carl Malamud <carl@media.org>
Message-Id: <200411262230.iAQMUOEv025523@bulk.resource.org>
In-Reply-To: <tsl7jo8qog0.fsf@cz.mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 26 Nov 2004 14:30:24 -0800
Organization: Memory Palace Press
X-Winch: Warn 9.5i
X-Mailer: ELM [version 2.4ME+ PL94 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

That seems simple enough when put that way ... then leave the executive director
totally out of this BCP or specify that the IESG names that person.  No need to
pussy-foot around the issue.  :)

Carl

> 
> 
> >>>>> "Carl" == Carl Malamud <carl@media.org> writes:
> 
> 
>     Carl> It seems to me that one of the goals of the whole AdminRest
>     Carl> exercise has been to move overall management responsibility
>     Carl> for IETF admin. and support activities (IASA) from
>     Carl> contractors to a "program manager", which is what this BCP
>     Carl> is all about.  As such, it seems that where documents refer
>     Carl> to "IETF Executive Director" that should become (via a
>     Carl> paragraph in this BCP) a pointer to the IAD or other
>     Carl> appropriate position as further pointed to by the IAD.
> 
> 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.
> 

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