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

Bob Hinden <bob.hinden@gmail.com> Mon, 19 February 2018 03:20 UTC

Return-Path: <bob.hinden@gmail.com>
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 820C4126C22 for <iasa20@ietfa.amsl.com>; Sun, 18 Feb 2018 19:20:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level:
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FIN_FREE=2.7, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tn7MpVcuRsZY for <iasa20@ietfa.amsl.com>; Sun, 18 Feb 2018 19:20:46 -0800 (PST)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF3731201FA for <iasa20@ietf.org>; Sun, 18 Feb 2018 19:20:45 -0800 (PST)
Received: by mail-wr0-x22c.google.com with SMTP id w77so8195984wrc.6 for <iasa20@ietf.org>; Sun, 18 Feb 2018 19:20:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Cyd6c8yNeiVGQ6ZycseNTI1AufTyEVgoH4SaNm2lvfw=; b=LO96v7GIXRCOj3d952CPru9oxueIGRSxOH/CZyUSCY91QRP3R9wwpDillfMm7gqux5 3cAXAIn9kdfG0tuoMMy5kpXlKSHOD1f4+dFnsY3mnR5LTnsI4bSwLw4zS/LndGfGekNS ge7RqfDHgFFtEIUhSBX4Lc7lZy7o8qtArGjOUOR6r9rFeGaEjhl3keYaNqzLraVr6jnW qAwrHOy94r6QFBvLUfQAc60drfM6wZkEQzdBd1T+P8/bS9+cJq+1+GVf7miUQ7/7w4RE oOkOZRaEqZZqMzpz0ruff9/yTq8gCSqYjIpi+kt0qDxr/MAv06Y28kUfyEY5I0igTPnD c82A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Cyd6c8yNeiVGQ6ZycseNTI1AufTyEVgoH4SaNm2lvfw=; b=jcwkhPuIpCr/8zBFk7VE8SYbWMnAtyYZIMXe31CDdLMXXSAFAGqlU4sZw+QJg8nZhq 6GlOFJpSYecGfq35y1FNTngpUEBVgvNUjW5dkHUfYTF/G4CQAzjPutHdBxm10Udkx9m3 Bv7yoe5JvHH4hiWEosDZk6mwQ+AqK7AjdhMO/WFoMzfGnjr/GSblSFbrWdii/Fo3A2im i7u23for6hM1pGrmD6oHa7raA2I4iZZqpJI/cla6DIPnH7N9GrpP/+Jmdxsm3MtrTd01 nk6yDarMMOUhofLMT1L8gtI8uOfmg/QcTxMuq66QNo1cdffXlglQexsCf52HR0kh4kdm YLMA==
X-Gm-Message-State: APf1xPADO+huJ/0BWZUVvd0QWt40sEk/JRUxgjfS1iV5ndCMa1CWMaoz iguPIlQ1k5IXQgBs2YOGooo=
X-Google-Smtp-Source: AH8x224jVBE5vVQRisocgR4nbi5XGKA/Xg/dCH4Dl049OnA60LNttMwhjAEnfG0oZBpiLs6WRDLkSw==
X-Received: by 10.223.162.203 with SMTP id t11mr7485426wra.88.1519010444210; Sun, 18 Feb 2018 19:20:44 -0800 (PST)
Received: from [172.25.3.70] (rrcs-67-52-140-5.west.biz.rr.com. [67.52.140.5]) by smtp.gmail.com with ESMTPSA id 2sm21281102wra.58.2018.02.18.19.20.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Feb 2018 19:20:42 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <207946BC-85B2-4E4F-BCA4-A4452A3BADA1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A81FAFCD-4E24-42F6-B8CD-548AC4F07950"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sun, 18 Feb 2018 19:20:40 -0800
In-Reply-To: <20180217134152.45fgwxqipuplwhp7@mx4.yitter.info>
Cc: Bob Hinden <bob.hinden@gmail.com>, iasa20@ietf.org
To: Andrew Sullivan <ajs@anvilwalrusden.com>
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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/CmRTEf7hCUG9WDzjMXR2RWJ4X18>
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: Mon, 19 Feb 2018 03:20:47 -0000

Andrew,

> On Feb 17, 2018, at 5:41 AM, Andrew Sullivan <ajs@anvilwalrusden.com> 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.

But that doesn’t really happen, it’s more the opposite.  If the IETF goes over the budget it sets for the year, ISOC picks up the difference.  In the current model, the IETF never has a deficit.  For example, in 2016 from iaoc.ietf.org, the budget for the year showed an ISOC contribution of $2.17M vs. the actuals of $2.43M, so ISOC contributed $263K more than the IETF said would be needed.

> 
> 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.

Yes, but isn’t that what is supposed to be happening now.  There are budgets and actuals on iaoc.ietf.org since the IASA was created.  It’s worth reading https://iaoc.ietf.org/documents/2016-IETF-Year-End-Commentary.pdf .

I agree is a lot to be done to work out the operational issues with any of the new models.

> 
> 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.

I agree, as long as we are willing to deal with the consequences.  In my view, it will require money to be given a lot more consideration that it does in the current model.

Bob