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

John C Klensin <john@jck.com> Wed, 08 September 2004 13:09 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 JAA09683; Wed, 8 Sep 2004 09:09:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C52GS-0000Cy-RE; Wed, 08 Sep 2004 09:13:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C525d-0001nv-AM; Wed, 08 Sep 2004 09:02:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C51z7-0000Ej-Op for ietf@megatron.ietf.org; Wed, 08 Sep 2004 08:55:38 -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 IAA08528 for <ietf@ietf.org>; Wed, 8 Sep 2004 08:55:31 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C522g-0008Mv-TH for ietf@ietf.org; Wed, 08 Sep 2004 08:59:20 -0400
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1C51yx-000JP5-1P; Wed, 08 Sep 2004 08:55:27 -0400
Date: Wed, 08 Sep 2004 08:55:26 -0400
From: John C Klensin <john@jck.com>
To: Brian E Carpenter <brc@zurich.ibm.com>, ietf@ietf.org
Message-ID: <2BEB37ED61ABF9F5FD672213@scan.jck.com>
In-Reply-To: <413EB2E7.3080109@zurich.ibm.com>
References: <200409071826.i87IQ7Fi016156@bulk.resource.org> <413EB2E7.3080109@zurich.ibm.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
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.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit


--On Wednesday, 08 September, 2004 09:21 +0200 Brian E Carpenter
<brc@zurich.ibm.com> wrote:

> Carl Malamud wrote:
>>> like many things outside the core technical field, these
>>> things are hard, and harder than they look, and hard enough
>>> that you need a better lawyer. as long as IETF remains an
>>> unincorporated association, i think you need every new IESG
>>> and IAB member to add their signature to all current MoU's
>>> and other agreements.  but you should find a lawyer.  a
>>> better lawyer than the one who was standing by last time
>>> this stuff was discussed or signed. -- 
>>> Paul Vixie
>>> 
>> 
>> 
>> What Paul says is sort of true.  Traditionally, at common
>> law, all members of an unincorporated association were, in
>> certain circumstances, personally liable for the actions of
>> the association.
> 
> 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


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