Re: What to incorporate (Re: Options for IETF administrative restructuring)

Susan Harris <srh@merit.edu> Thu, 02 September 2004 14:55 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 KAA09930; Thu, 2 Sep 2004 10:55:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2t1s-0002Pb-0n; Thu, 02 Sep 2004 10:57:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2srl-0002zB-De; Thu, 02 Sep 2004 10:47:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2scy-00063K-3U for ietf@megatron.ietf.org; Thu, 02 Sep 2004 10:31:52 -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 KAA07741 for <ietf@ietf.org>; Thu, 2 Sep 2004 10:31:50 -0400 (EDT)
Received: from backin5.merit.edu ([198.108.60.28]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2sfK-0000L4-Kx for ietf@ietf.org; Thu, 02 Sep 2004 10:34:21 -0400
Received: by backin5.merit.edu (Postfix, from userid 8935) id A2A347E50C; Thu, 2 Sep 2004 10:31:47 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by backin5.merit.edu (Postfix) with ESMTP id 8C72429ADA; Thu, 2 Sep 2004 10:31:47 -0400 (EDT)
Date: Thu, 02 Sep 2004 10:31:47 -0400
From: Susan Harris <srh@merit.edu>
To: Carl Malamud <carl@media.org>
In-Reply-To: <200409021417.i82EHHKZ001620@bulk.resource.org>
Message-ID: <Pine.GSO.4.58.0409021030050.5266@backin5.merit.edu>
References: <200409021417.i82EHHKZ001620@bulk.resource.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ietf@ietf.org
Subject: Re: What to incorporate (Re: Options for IETF administrative restructuring)
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: 8abaac9e10c826e8252866cbe6766464

> Just so we're clear, that was my going-in assumption and I've kept
> that throughout the analysis.  Any of the structures I've outlined

Understood.

> can be focused strictly on administrative support (just like
> any of the structures could be corrupted to reach beyond that
> focus).  That's why I suggested that we do this in two steps:
>
> 1. agree on the general direction to take
> 2. task people to write the specific chartering documents and
>    publish them as a bcp, including a last call
>
> Since the devil is in the details, this lets us focus in
> on making sure the details are correct and the community has
> seen those details and agreed to them before they become policy.
> First step, though, is some feeling from the community on which
> path to pursue.
>
> Make sense?  (BTW, I'm more than happy to answer questions

Absolutely.  I thought your report was excellent - very clear and concise.
(Long though - how'd you manage it it such a short time :)

> about these various mechanisms, processes, functions, and
> other buzzwords in the report ... I tried to keep things
> clear, but the legal world isn't always perfectly clear. :)

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