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

Brian E Carpenter <brc@zurich.ibm.com> Wed, 08 September 2004 08:35 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 EAA20475; Wed, 8 Sep 2004 04:35:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4xym-0003RD-4n; Wed, 08 Sep 2004 04:39:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4xrN-0001wO-N7; Wed, 08 Sep 2004 04:31:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4xpg-0001TJ-1f for ietf@megatron.ietf.org; Wed, 08 Sep 2004 04:29:36 -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 EAA20029 for <ietf@ietf.org>; Wed, 8 Sep 2004 04:29:32 -0400 (EDT)
Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4xtF-0003Ja-Ep for ietf@ietf.org; Wed, 08 Sep 2004 04:33:19 -0400
Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1]) by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id i888T1FW034516 for <ietf@ietf.org>; Wed, 8 Sep 2004 08:29:01 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i888T1JR214078 for <ietf@ietf.org>; Wed, 8 Sep 2004 10:29:01 +0200
Received: from zurich.ibm.com (dyn-9-155-46-122.mainz.de.ibm.com [9.155.46.122]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id KAA19580 for <ietf@ietf.org>; Wed, 8 Sep 2004 10:29:00 +0200
Message-ID: <413EB2E7.3080109@zurich.ibm.com>
Date: Wed, 08 Sep 2004 09:21:11 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: ietf@ietf.org
References: <200409071826.i87IQ7Fi016156@bulk.resource.org>
In-Reply-To: <200409071826.i87IQ7Fi016156@bulk.resource.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

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.

     Brian

> 
> However, under the 1996 uniform nonprofit unincorporated association act, 
> which has been passed by 9 states, unincorpated associations can,
> under certain circumstances, have standing, limitations of liability,
> and the ability to hold and transfer property.
> 
> The -01 rev of my draft, to be released shortly, contains more details on this 
> mechanism.  
> 
> Regards,
> 
> Carl
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 


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