Re: Options for IETF administrative restructuring

avri@psg.com Tue, 07 September 2004 13:27 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 JAA20871; Tue, 7 Sep 2004 09:27:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4g4B-00044F-L0; Tue, 07 Sep 2004 09:31:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4fou-0006PC-Ju; Tue, 07 Sep 2004 09:15:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4fkR-0005Gf-Oz for ietf@megatron.ietf.org; Tue, 07 Sep 2004 09:10:59 -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 JAA19608 for <ietf@ietf.org>; Tue, 7 Sep 2004 09:10:50 -0400 (EDT)
From: avri@psg.com
Received: from tla.crepundia.net ([194.71.127.149] helo=report.tla-group.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4fnl-0003lv-1U for ietf@ietf.org; Tue, 07 Sep 2004 09:14:26 -0400
Received: from [127.0.0.1] (report.tla-group.com [194.71.127.149]) by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i87Cr4ep024808 for <ietf@ietf.org>; Tue, 7 Sep 2004 14:53:05 +0200
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <413D5184.5050600@zurich.ibm.com>
References: <3D67CCA7D63E714B980D21A038EEA08E0EF5612E@i2km02-ukbr.domain1.systemhost.net> <F87F19A0-0016-11D9-AF33-000393CC2112@psg.com> <413D5184.5050600@zurich.ibm.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <552594C4-00CF-11D9-AF33-000393CC2112@psg.com>
Content-Transfer-Encoding: 7bit
Date: Tue, 07 Sep 2004 09:10:47 -0400
To: ietf@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: 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.3 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

On 7 sep 2004, at 02.13, Brian E Carpenter wrote:

> avri@psg.com wrote:
>>
>
> I'm very puzzled. I though those two extremes were exactly described
> by scenarios A and D.

Perhaps I misread, but while I saw that A and D are the extremes of the 
scenarios represented to date, I was suggesting is that the extremes 
not yet discussed are:

- full integration into ISOC with the rework of the by-law that 
accommodates the standard's function. Scenario A tends toward this but 
does, seem to me, to go all the way.

- Creation of a parallel non profit incorporated Standards organization 
with its own by-laws  that is partnered though MOU's with ISOC.  
Scenario D might evoke this, but since the explanation of this Scenario 
is so brief, I have trouble understanding its implications.

In both I have trouble understanding the full implications in terms of 
items not within the administrative domain.

If A really does equal full integration and D really does equal full 
independence, then I will stand corrected, though I will remain 
confused about some of the implications.


a.


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