Re: There is no proposal on the table for *IETF* incorporation (Was: Explosive bolts [Re: Options for IETF administrative restructuring]

"Lynn St.Amour" <st.amour@isoc.org> Mon, 13 September 2004 23:41 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 TAA25319; Mon, 13 Sep 2004 19:41:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C70WV-0007R4-IB; Mon, 13 Sep 2004 19:46:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C705e-0007LI-TU; Mon, 13 Sep 2004 19:18:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6zwL-0005ED-Th for ietf@megatron.ietf.org; Mon, 13 Sep 2004 19:08:53 -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 TAA23620 for <ietf@ietf.org>; Mon, 13 Sep 2004 19:08:50 -0400 (EDT)
Received: from mail3.bluewin.ch ([195.186.1.75]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7017-0006tG-T5 for ietf@ietf.org; Mon, 13 Sep 2004 19:13:51 -0400
Received: from [192.168.1.34] (83.78.9.251) by mail3.bluewin.ch (Bluewin AG 7.0.030.2) id 41459DC2000144B1; Mon, 13 Sep 2004 23:08:07 +0000
Mime-Version: 1.0
X-Sender: st.amour@pop.bluewin.ch
Message-Id: <a0600183abd6bc5367bc8@[192.168.1.34]>
In-Reply-To: <p06200932bd652dda966a@[216.43.25.67]>
References: <200409071826.i87IQ7Fi016156@bulk.resource.org> <413EB2E7.3080109@zurich.ibm.com> <2BEB37ED61ABF9F5FD672213@scan.jck.com> <a06001825bd64f848f822@[10.0.1.4]> <p06200932bd652dda966a@[216.43.25.67]>
Date: Tue, 14 Sep 2004 01:08:04 +0200
To: Pete Resnick <presnick@qualcomm.com>
From: "Lynn St.Amour" <st.amour@isoc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Lynn DuVal <duval@isoc.org>, John C Klensin <john@jck.com>, ietf@ietf.org
Subject: Re: There is no proposal on the table for *IETF* incorporation (Was: Explosive bolts [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: 4adaf050708fb13be3316a9eee889caa

At 4:49 PM -0500 9/8/04, Pete Resnick wrote:
>On 9/8/04 at 4:54 PM -0400, Lynn St.Amour wrote:
>
>>Should the IETF incorporate as a separate entity...
>
>To date, there has been no proposal, in Carl's document or otherwise 
>as far as I know, for *the IETF* to incorporate as a separate 
>entity. There have been proposals to incorporate a body to deal with 
>IETF administrative functions (like contracting for meetings, 
>contracting for ISP and web service, etc.), referred to in Carl's 
>document as "IETF Foundation". Incorporating that sort of entity 
>wouldn't change the insurance coverage for members of the IETF, 
>would it?
>
>pr
>--

Thanks Pete,

I did mean the IETF Admin entity, despite the 'shorthand' terminology above.

I had ISOC's Director of Finance - Lynn DuVal expand upon the earlier 
response.  Her response is below.

Yes,  incorporating the administrative functions of the IETF will 
require that they obtain their own insurance policy.   Once, a 
separate entity is formed, it requires its own federal identification 
number and hence its own insurance policy.  (Doesn't matter if it is 
incorporated as a non-profit, for profit or as a foundation.)     If 
the admin. entity does only admin, then they would need coverage 
which protects the officers against errors & omissions in the admin. 
area only.   ISOC could continue to cover any Standards activities. 
We would just need to be very specific about the split of 
responsibilities between the organizations to ensure that the 
policies were properly aligned.

Regards,

Lynn



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