IETF Logo Mail Archive

Re: Explosive bolts [Re: Options for IETF administrativerestructuring]

Brian E Carpenter <brc@zurich.ibm.com> Wed, 08 September 2004 08:48 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 EAA21298; Wed, 8 Sep 2004 04:48:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4yC3-0003h4-1M; Wed, 08 Sep 2004 04:52:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4xrR-0001y8-GN; Wed, 08 Sep 2004 04:31:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4xpg-0001TK-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 EAA20032 for <ietf@ietf.org>; Wed, 8 Sep 2004 04:29:32 -0400 (EDT)
Received: from mtagate3.de.ibm.com ([195.212.29.152]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4xtF-0003Jd-Q3 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 mtagate3.de.ibm.com (8.12.10/8.12.10) with ESMTP id i888T2nO129104 for <ietf@ietf.org>; Wed, 8 Sep 2004 08:29:02 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 i888T1JR214080 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 KAA34576 for <ietf@ietf.org>; Wed, 8 Sep 2004 10:29:01 +0200
Message-ID: <413EB38F.6050503@zurich.ibm.com>
Date: Wed, 08 Sep 2004 09:23:59 +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: <20040907153406.851C97CDD1@newdev.harvard.edu>
In-Reply-To: <20040907153406.851C97CDD1@newdev.harvard.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: Re: Explosive bolts [Re: Options for IETF administrativerestructuring]
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: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

scott bradner wrote:
>>In his scenario, not only the Administrative Czar would need explosive
>>bolts, but also the RFC Editor and Secretariat, etc. 
> 
> 
> that depends on the contracts with those suppliers - if the contract
> is signed by the IETF chair or the admin czar for the IETF (rather than
> for the ISOC) I would not expect that any supplier-specific bolts would
> be required

And it would be pretty simple for ISOC (our incorporated entity designed
for this purpose in 1992) to give formal signature rights to the IETF
chair if we really needed that. I think a Board resolution would suffice.

    Brian


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

v2.14.0 | Report a Bug | By Email