RE: Scenario O Re: Upcoming: further thoughts on where from here
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 23 September 2004 15: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 LAA23452; Thu, 23 Sep 2004 11:35:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVkF-0002CL-TW; Thu, 23 Sep 2004 11:42:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAVQ5-0007H9-7t; Thu, 23 Sep 2004 11:22:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAVHc-0005af-Jv for ietf@megatron.ietf.org; Thu, 23 Sep 2004 11:13:20 -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 LAA21493 for <ietf@ietf.org>; Thu, 23 Sep 2004 11:13:17 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVOQ-0001ex-0k for ietf@ietf.org; Thu, 23 Sep 2004 11:20:22 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id i8NFCja6021090 for <ietf@ietf.org>; Thu, 23 Sep 2004 10:12:46 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <RLRKKP8V>; Thu, 23 Sep 2004 17:12:45 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C79CC7@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "'Joel M. Halpern'" <joel@stevecrocker.com>, ietf@ietf.org
Date: Thu, 23 Sep 2004 17:12:38 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: RE: Scenario O Re: Upcoming: further thoughts on where from here
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
Joel... just to be clear... I suspect that in the below you meant IASA (IETF Administrative Support Activity) which is defined in Scenario O and not IASF (IETF Administartive Support Foundation) which is defined in Scenario C Bert > -----Original Message----- > From: Joel M. Halpern [mailto:joel@stevecrocker.com] > Sent: Thursday, September 23, 2004 16:35 > To: ietf@ietf.org > Subject: Re: Scenario O Re: Upcoming: further thoughts on where from > here > > > I think that this (scenario 0) is the right approach to > follow. It appears > to me to be the lowest risk path consistent with the needs > that have been > identified. > > > Two minor comments: > 1) The references to "the IASF bank account" should probably be relaxed to > "IASF fund accounts" or "IASF accounts". As written, it presumes that > there is exactly one bank account, and that separation of funds is by bank > control. While the later is probably a good idea, I don't think this BCP > is the place to call that out. And the exact number of bank accounts used > by IASF (0, 1, 5, or ...) is not a concern for this BCP. > > 2) The schedule calls for seating the IAOC on January 15, and hiring the > IAD by the end of January. Given that the search committee can not be > appointed until the board is seated, it seems that item is either an > impossible schedule or assumes facts not in evidence. > > Yours, > Joel M. Halpern _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: Scenario O Re: Upcoming: further thoughts on … Margaret Wasserman
- RE: Scenario O Re: Upcoming: further thoughts on … Wijnen, Bert (Bert)
- RE: Scenario O Re: Upcoming: further thoughts on … Joel M. Halpern
- RE: Scenario O Re: Upcoming: further thoughts on … Wijnen, Bert (Bert)
- RE: Scenario O Re: Upcoming: further thoughts on … John C Klensin
- RE: Scenario O Re: Upcoming: further thoughts on … John C Klensin
- RE: Scenario O Re: Upcoming: further thoughts on … scott bradner
- RE: Scenario O Re: Upcoming: further thoughts on … Wijnen, Bert (Bert)
- RE: Scenario O Re: Upcoming: further thoughts on … Tony Hain
- RE: Scenario O Re: Upcoming: further thoughts on … Jeffrey Hutzelman