Re: AdminRest: IASA BCP: Finances and Accounting - principles

John C Klensin <john-ietf@jck.com> Sun, 28 November 2004 16:29 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 LAA25743; Sun, 28 Nov 2004 11:29:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYS0L-0005Y5-3V; Sun, 28 Nov 2004 11:34:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYRrP-0003zk-R9; Sun, 28 Nov 2004 11:25:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYRms-0003Fw-22 for ietf@megatron.ietf.org; Sun, 28 Nov 2004 11:20:34 -0500
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 LAA25253 for <ietf@ietf.org>; Sun, 28 Nov 2004 11:20:32 -0500 (EST)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYRra-0005GE-6T for ietf@ietf.org; Sun, 28 Nov 2004 11:25:27 -0500
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1CYRmn-000I0J-Vd; Sun, 28 Nov 2004 11:20:29 -0500
Date: Sun, 28 Nov 2004 11:20:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: Valdis.Kletnieks@vt.edu, Sam Hartman <hartmans-ietf@mit.edu>
Message-ID: <3ACA2F159ACC206BD78CA35B@scan.jck.com>
In-Reply-To: <200411270108.iAR18lUX014366@turing-police.cc.vt.edu>
References: <24324E11F12B543653F369BF@7AD4D3FB4841A5E367CCF211> <tslhdncno1x.fsf@cz.mit.edu> <200411270108.iAR18lUX014366@turing-police.cc.vt.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: AdminRest: IASA BCP: Finances and Accounting - principles
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: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit


--On Friday, 26 November, 2004 20:08 -0500
Valdis.Kletnieks@vt.edu wrote:

> On Fri, 26 Nov 2004 19:16:58 EST, Sam Hartman said:
> 
>> Personally, I do believe that stating some details would help
>> me evaluate whether IASA is seperable and would require the
>> IETF's consent in order to change the details.  I do think
>> that requiring IASA keep separate bank accounts is probably
>> desirable at the BCP level.
> 
> OK - I admit I've Just Hit Delete on much of this discussion -
> but care has to be taken with "separate bank accounts".  We
> *do* need some way to prevent IASA from separating (either at
> their request or ours) and then find out all the money was in
> "their" account not "ours"....
> 
> (OK.. maybe I'm just paranoid on that one, having been on the
> losing end of a "been there done that" in my personal life. :)

This is interesting.  Almost all of the discussion about
"separate bank accounts", etc., has been focused on "protection
of the IASA from ISOC".  But you drew the other inference, which
I discussed at more length in my "blowing the bolts" note, i.e.,
that it is at least as likely that the IETF might need
protection from the IASA or even, once large amounts of money
are involved, from some combination of the IAB, IESG, and IASA.

   john






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