IETF Logo Mail Archive

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

Harald Tveit Alvestrand <harald@alvestrand.no> Thu, 02 September 2004 10:40 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 GAA20176; Thu, 2 Sep 2004 06:40:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2p3D-0006YV-V3; Thu, 02 Sep 2004 06:42:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2oqR-0000kO-Lz; Thu, 02 Sep 2004 06:29:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2oeA-0002Kq-Jf for ietf@megatron.ietf.org; Thu, 02 Sep 2004 06:16:50 -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 GAA18556 for <ietf@ietf.org>; Thu, 2 Sep 2004 06:16:48 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2ogW-0004a4-TB for ietf@ietf.org; Thu, 02 Sep 2004 06:19:18 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1DC9461BB5; Thu, 2 Sep 2004 12:16:17 +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 22295-04; Thu, 2 Sep 2004 12:16:15 +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 7187861BAF; Thu, 2 Sep 2004 12:16:13 +0200 (CEST)
Date: Thu, 02 Sep 2004 12:16:19 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Brian E Carpenter <brc@zurich.ibm.com>
Message-ID: <77160AB1CBDE5AE8E27F638D@askvoll.hjemme.alvestrand.no>
In-Reply-To: <4136EF7F.6020600@zurich.ibm.com>
References: <F74255F42647ECBAAC5E9C87@B50854F0A9192E8EC6CDA126> <4136EF7F.6020600@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: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: 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.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit


--On torsdag, september 02, 2004 12:01:35 +0200 Brian E Carpenter 
<brc@zurich.ibm.com> wrote:

> Christian also implies the converse question: would scenarios C & D
> reduce a hypothetical existing conflict of interest for the ISOC
> trusteees? Again, I don't see why. Firstly, I don't think there is
> an existing conflict of interest. Secondly, changing the IETF from
> an unincorporated association to an incorporated entity really
> cannot affect the ISOC trustees' fiduciary duty to ISOC, so any
> hypothetical conflict would not be changed.

one note, since this has been a repeated source of much confusion and 
miscommunication....

scenarios C and D envision incorporating the *support function* for the 
IETF. The IETF would remain an undefined entity under these scenarios.

I've had another suggestion that the IETF (the real technical process 
entity) should become a formally recognizable entity of some sort (possibly 
an unincorporated organization). But that's distinct from the idea of 
incorporating the support function, and is NOT described in the current 
document.

If people want that possibility described, please speak up - Carl has the 
pen ready....


                             Harald


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

v2.23.0 | Report a Bug | By Email