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

Pete Resnick <presnick@qualcomm.com> Tue, 07 September 2004 14:30 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 KAA25964; Tue, 7 Sep 2004 10:30:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4h3E-00058g-RM; Tue, 07 Sep 2004 10:34:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4gwB-0002TC-0G; Tue, 07 Sep 2004 10:27:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4gsm-0001IW-SY for ietf@megatron.ietf.org; Tue, 07 Sep 2004 10:23:41 -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 KAA25442 for <ietf@ietf.org>; Tue, 7 Sep 2004 10:23:38 -0400 (EDT)
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4gwE-00052e-RU for ietf@ietf.org; Tue, 07 Sep 2004 10:27:15 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server X 3.2.5); Tue, 7 Sep 2004 09:23:09 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p06200915bd636fbd07d4@[216.43.25.67]>
In-Reply-To: <413D5111.9010807@zurich.ibm.com>
References: <7D5D48D2CAA3D84C813F5B154F43B1550526B0E7@nl0006exch001u.nl.lucent.com> <413C61EF.3080208@zurich.ibm.com> <p06200912bd62c7318705@[216.43.25.67]> <413D5111.9010807@zurich.ibm.com>
X-Mailer: Eudora [Macintosh version 6.2a9]
Date: Tue, 07 Sep 2004 09:23:06 -0500
To: Brian E Carpenter <brc@zurich.ibm.com>
From: Pete Resnick <presnick@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ietf@ietf.org
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: 7aafa0432175920a4b3e118e16c5cb64

As Brian, I will leave aside the question of whether the lawyers can 
make it possible for an MoU to be effective; I'm not a lawyer either. 
However, I think we may have different definitions of "explosive 
bolts":

On 9/7/04 at 8:11 AM +0200, Brian E Carpenter wrote:

>Here's a version of what the explosive bolts could look like.
>
>...MOU with ICANN...
>
>...that MOU contains explosive bolts. So far, we haven't had to explode them.
>
>>    2. This MOU will remain in effect until either modified or 
>>cancelled by mutual consent of the Internet Engineering Task Force 
>>and the Internet Corporation for Assigned Names and Numbers, or 
>>cancelled by either party with at least six (6) months notice.

This doesn't look so much to be "explosive bolts", but rather a 
"self-destruct mechanism"; when either side decides that they don't 
want to participate, the agreement blows up and any structures 
between the two organizations evaporate. When I talk about "explosive 
bolts", I mean having some way to separate the IETF administrative 
function housed in ISOC from ISOC.

For example, let's say that scenario A or B end up having an employee 
of ISOC whose title is "IETF Administrative Czar", and she has 5 
employees working under her (an accountant, a lawyer, a secretary, 
etc.). What I'd want out of an "explosive bolts" agreement is that, 
if one side or the other wants to pull the plug, the Czar and the 5 
employees continue to act at the behest of the IETF (*not* ISOC) and 
there is some way to spin off a subsidiary of ISOC into a separate 
entity so that the IETF continues to get administrative support from 
these folks. Current contracts would have to continue to function, 
upcoming meetings would have to continue uninterrupted, and most 
importantly the IETF does not have to go through another 
administrative restructuring like we're doing now in order to have 
things continue to operate.

Perhaps I'm more interested in the administrative function having an 
"escape pod", and the whole thing is attached to ISOC with explosive 
bolts. The key, to repeat it again, is that we don't have to go 
through another administrative restructuring if a future IETF or ISOC 
decide they can't live with each other anymore.

pr
--
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

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