Re: Explosive bolts [Re: Options for IETF administrativerestructuring]
Pete Resnick <presnick@qualcomm.com> Wed, 08 September 2004 17:46 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 NAA00876; Wed, 8 Sep 2004 13:46:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C56aS-0005aD-Pz; Wed, 08 Sep 2004 13:50:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C56P3-0004fD-GQ; Wed, 08 Sep 2004 13:38:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C56LN-0003pm-5h for ietf@megatron.ietf.org; Wed, 08 Sep 2004 13:34:53 -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 NAA00030 for <ietf@ietf.org>; Wed, 8 Sep 2004 13:34:51 -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 1C56P3-0005MP-2t for ietf@ietf.org; Wed, 08 Sep 2004 13:38:42 -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) for <ietf@ietf.org>; Wed, 8 Sep 2004 12:34:20 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p06200925bd64dc73825d@[216.43.25.67]>
In-Reply-To: <413EB38F.6050503@zurich.ibm.com>
References: <20040907153406.851C97CDD1@newdev.harvard.edu> <413EB38F.6050503@zurich.ibm.com>
X-Mailer: Eudora [Macintosh version 6.2a9]
Date: Wed, 08 Sep 2004 12:34:18 -0500
To: ietf@ietf.org
From: Pete Resnick <presnick@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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: 3e15cc4fdc61d7bce84032741d11c8e5
On 9/8/04 at 9:23 AM +0200, Brian E Carpenter wrote: >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)... This is the most utterly confusing thing I've heard on this topic and I really hope Scott can clarify: 1. As far as I can tell, there is no scenario in which the IETF chair is signing anything. First and foremost, the IETF chair can't make a contract without exposing him/herself to *personal* liability because the IETF chair (as such) is not an employee of any corporation which empowers such a thing. If I were IETF chair, I wouldn't sign any contract which came within 10 miles of me. 2. The admin czar (at least in scenarios A&B) would be an employee of ISOC. I don't see how that person could possibly sign a contract on behalf of the IETF: Like the IETF chair, there's no legal relationship there that I understand. The admin czar could sign a contract on behalf of ISOC, or under scenario C&D sign on behalf of the "IETF Foundation" (as Carl's report calls it). So I have no idea what you could mean by "sign for the IETF". And this is the core of my concern. >>I would not expect that any supplier-specific bolts would be required If all contracts (including the RFC Editor and the Secretariat) went through the admin entity (which would be under the ISOC in A&B), I agree that no separate bolts are 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. But that would entail giving the IETF chair signature rights *to sign for ISOC*. That would be sufficient for these purposes, but is completely undesirable in that we were trying to get IAB/IESG members *out* of the business of administrative tasks. 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
- RE: Explosive bolts [Re: Options for IETF adminis… graham.travers
- Explosive bolts [Re: Options for IETF administrat… scott bradner
- Re: Explosive bolts [Re: Options for IETF adminis… Brian E Carpenter
- Re: Explosive bolts [Re: Options for IETF adminis… Pete Resnick
- Re: Explosive bolts [Re: Options for IETF adminis… scott bradner
- Re: Explosive bolts [Re: Options for IETF adminis… Pete Resnick