Re: [Iasa20] Memo exploring options for IASA 2.0 models

Brian Carpenter <brian@cs.auckland.ac.nz> Sat, 17 February 2018 19:28 UTC

Return-Path: <brian@cs.auckland.ac.nz>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33AE12422F for <iasa20@ietfa.amsl.com>; Sat, 17 Feb 2018 11:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.021
X-Spam-Level:
X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FIN_FREE=2.289, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szcW5sYG6ntz for <iasa20@ietfa.amsl.com>; Sat, 17 Feb 2018 11:28:28 -0800 (PST)
Received: from mx3-int.auckland.ac.nz (mx3-int.auckland.ac.nz [130.216.125.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69C9D120454 for <iasa20@ietf.org>; Sat, 17 Feb 2018 11:28:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1518895708; x=1550431708; h=from:subject:to:references:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=0dMvgTstvs72rvk20RGNn3yR5Xrr25bG4crDpBm2hEc=; b=nud2A5g6wEGotjYqXB+vMrDBnzvdah5oP/48zKqOtoOFZkneqEnqEiEw zuhMY5+Brkojwo3EAYW0NuJB20+5ec3zL5/GpaSztgJA4jjpUFWfMwVKG HuWMtgB1yKjslmyIXM8hfaPQBM0VnD5iWTHaWS772TtiBNDz01NOlgL3A ooXdosPcOO3IkTnJsqmdBFpcPau3z47/YWmBi0KW/N58vgQZq2EwXSgVI krYOyraObpsQLJk37STZhrlU6FdEWfjoDyZorT+l1nwgdWkJ7ReVMNlqz 5iMZZNvBZWcyctVP5/KFI5RX6tXZJRQVPGEabojH+Wo1TfyqsNZXxZ6kA g==;
X-IronPort-AV: E=Sophos;i="5.46,526,1511780400"; d="scan'208";a="10865977"
X-Ironport-HAT: BAD-REPUTATION - $RELAY-AUTH-THROTTLE
X-Ironport-Source: 111.69.224.122 - Outgoing - Outgoing-SSL
Received: from 122.224.69.111.dynamic.snap.net.nz (HELO [192.168.178.30]) ([111.69.224.122]) by mx3-int.auckland.ac.nz with ESMTP; 18 Feb 2018 08:28:24 +1300
From: Brian Carpenter <brian@cs.auckland.ac.nz>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, iasa20@ietf.org
References: <20182.1518727709@obiwan.sandelman.ca> <C77B41DA-268D-4F0E-8AC8-F2E292E38B14@cooperw.in> <9631.1518800971@obiwan.sandelman.ca> <be961111-9bed-086e-a0ab-b220125a438d@cs.auckland.ac.nz> <20180216185551.cgigor7up7uowmr6@mx4.yitter.info> <40a7ffe5-8417-cfdf-15dc-6603a5c7978f@cs.auckland.ac.nz> <20180216192334.jjgn6bineinfofux@mx4.yitter.info> <5327daa0-1d54-f051-e620-7c8f4bdc4870@cs.auckland.ac.nz> <20180216223021.jxetl5cz4uzem24c@mx4.yitter.info> <5657276F-E288-42C7-ABA1-5F0A16557B49@gmail.com> <20180217134152.45fgwxqipuplwhp7@mx4.yitter.info>
Organization: University of Auckland
Message-ID: <41c52c21-77fb-349a-03f7-4b07fcd654bc@cs.auckland.ac.nz>
Date: Sun, 18 Feb 2018 08:28:21 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180217134152.45fgwxqipuplwhp7@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/xSUK9xQE9qh7CUWNCjV99WMZ9ao>
Subject: Re: [Iasa20] Memo exploring options for IASA 2.0 models
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Feb 2018 19:28:30 -0000

On 18/02/2018 02:41, Andrew Sullivan wrote:
> On Fri, Feb 16, 2018 at 03:00:08PM -0800, Bob Hinden wrote:
>>
>> Seems to me that as long as ISOC provides most of the support for the IETF (and I think that true in each options presented), doesn’t this just morph into "ISOC is paying for the IETF, I gave money to the ISOC, why are you asking me again?".  Unless we are financially independent of ISOC, I don’t think moving to a new entity will really change this.
>>
> 
> I don't think that's right.  Your argument depends on the "fungible
> funds" stance, which is indeed a current problem.  Even people who
> understand how to earmark funds donated to ISOC for the IETF currently
> argue that this just allows ISOC to redirect money that _would_ have
> gone to the IETF to some other activity.
> 
> Now, we have not discussed the practicalities of operating under any
> of the new models, but I would anticipate an arrangement in which the
> IETFAdminOrg had responsibility for some budget and operating within
> it.  This would mean ensuring that the IETF account (rather than the
> ISOC general account) was funded appropriately to meet the IETF needs.
> Money could flow back and forth across that boundary still, but it
> would be a more formal process and would necessitate more obvious
> controls.

fwiw, I strongly agree with that. It's clearly a problem today. My
concern is about how much overhead & complexity we get when solving it.
 
> This would quite likely mean that some of the historical tendency to
> figure out what to spend and then figure out how much money we needed
> to ask ISOC for would need to change, at least over time.  In my
> opinion, that sort of discipline would not be a bad thing.

+1
   Brian
 
> Best regards,
> 
> A
>