IETF Logo Mail Archive

Re: Explosive bolts [Re: Options for IETF administrative restructuring]

"Lynn St.Amour" <st.amour@isoc.org> Wed, 08 September 2004 21: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 RAA24202; Wed, 8 Sep 2004 17:41:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5AGE-0003pd-9f; Wed, 08 Sep 2004 17:45:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C59ku-0000IJ-UJ; Wed, 08 Sep 2004 17:13:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C59TU-0002eK-Vf for ietf@megatron.ietf.org; Wed, 08 Sep 2004 16:55:29 -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 QAA20270 for <ietf@ietf.org>; Wed, 8 Sep 2004 16:55:26 -0400 (EDT)
Received: from sccrmhc13.comcast.net ([204.127.202.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C59XC-0002ae-Rp for ietf@ietf.org; Wed, 08 Sep 2004 16:59:20 -0400
Received: from [10.0.1.2] (pcp02192886pcs.reston01.va.comcast.net[68.48.94.247]) by comcast.net (sccrmhc13) with ESMTP id <2004090820545601600hs91ae>; Wed, 8 Sep 2004 20:54:56 +0000
Mime-Version: 1.0
X-Sender: st.amour@pop.bluewin.ch
Message-Id: <a06001825bd64f848f822@[10.0.1.4]>
In-Reply-To: <2BEB37ED61ABF9F5FD672213@scan.jck.com>
References: <200409071826.i87IQ7Fi016156@bulk.resource.org> <413EB2E7.3080109@zurich.ibm.com> <2BEB37ED61ABF9F5FD672213@scan.jck.com>
Date: Wed, 08 Sep 2004 16:54:52 -0400
To: John C Klensin <john@jck.com>, Brian E Carpenter <brc@zurich.ibm.com>, ietf@ietf.org
From: "Lynn St.Amour" <st.amour@isoc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: Re: 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.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

At 8:55 AM -0400 9/8/04, John C Klensin wrote:
>--On Wednesday, 08 September, 2004 09:21 +0200 Brian E Carpenter
><brc@zurich.ibm.com> wrote:
>
>  >
>>  And that's exactly why the liability insurance policy held by
>  > ISOC covers IETF "officials" today.
>
>Would someone who actually knows or can find out care to comment
>on whether the insurance would cover such "officials" if they
>started engaging in direct, large-scale, financial management
>and/or the direct supervision of those who were doing so, in
>addition to standards activities?
>
>       john


The ISOC Directors & Officers insurance presently covers the IETF, 
IESG, IAB, IRTF, IRSG and IANA (IETF related) "officials", and the 
RFC Editor.   It extends to the level of Working Group chairs and 
also covers the NomComm process (including Recall Committees).  This 
coverage would extend to financial management and/or direct 
supervision of those doing so in addition to standards activities, so 
long as the IETF was an unincorporated entity and was  operating 
under the "umbrella" of ISOC (as you are today).  Should the IETF 
incorporate as a separate entity, it would (obviously) no longer be 
covered under the ISOC insurance policy, but would require its own.

Regards,

Lynn

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

v2.23.0 | Report a Bug | By Email