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

Bob Hinden <bob.hinden@gmail.com> Mon, 19 February 2018 03:27 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 943341270A3 for <iasa20@ietfa.amsl.com>; Sun, 18 Feb 2018 19:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level:
X-Spam-Status: No, score=0.7 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, 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 8kgRxyqkjteh for <iasa20@ietfa.amsl.com>; Sun, 18 Feb 2018 19:27:43 -0800 (PST)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 614A91201FA for <iasa20@ietf.org>; Sun, 18 Feb 2018 19:27:43 -0800 (PST)
Received: by mail-wr0-x231.google.com with SMTP id v65so8177972wrc.11 for <iasa20@ietf.org>; Sun, 18 Feb 2018 19:27:43 -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=FIJHsOPOUom+1nNoPVh4RahWcpLfbL+XpHB++7zEhkg=; b=MaE6e05xCaNQl63FxUsv+BQCNrPTtQFz3dl5LlhrtYMIN/VR2kWIvgG1LBWsKOL2m/ xOd/BxlNZl77mX4AAzjOM0Ky55vqUfwFx+akbkuRGFvhHSogGx6Yw4VkxsDTByy346LM oCmjGE/g60SyVmyTKgD87KZ009JwG6aSNWqNgMCUjWAkE2llUdn+2jwnXsDC0T8A+Uac hUUJK1aJP0I2LQ1/Us/h4AofowlZEwIs+jcJ5CaZRL39h6QFq92aK6PCMCCHbuwumgUX eBEAzjlwmXXN98aWlqdEux1roUPsXXRD5MlZm6Ch4nUX9Kq3CvqE7ypDDiRLWgnAfqTX 1aEQ==
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=FIJHsOPOUom+1nNoPVh4RahWcpLfbL+XpHB++7zEhkg=; b=QZBwyPq6MCQ/A36YIVKAl24relsiF9ohrMa3kW0fD0D05urwEaj4RCMojnP6dP0zIM 042m8NsR/6niYG15uHxH1gmV3/TlOmehpOnJXjt1w11RC8uv3wHWabwOug4u3aZAFGXw HUhv5fPYuvyvr8Opw88lQVZySDveH6pgeQRNkBBe66UbmyYVAlHwPyTzfOXc/8zW6uR0 wkjvD7+Kj9byeYZoUgVuTc93I+8FV1III6bJhDC/vKwapgYcpGbJxCLD8gFVhvxnJErn 4Bxf+vN3xvV5XWqAi+tmldWbluNA0TBCpxBF71u5TtK63C2N34EIcRq+7iIbAIwdnrZW 3fIg==
X-Gm-Message-State: APf1xPCVVtT+0rQ3BLbjLp0RfnhM9FPkE34NescPQ9REM1VvNFeA3Uti ZEDADITm28KRDIazWpVC+zA=
X-Google-Smtp-Source: AH8x227PDGhUCJEru5mXgCNv67kD/y7zRnXQhn7vqpvrWoUs3hhezSoZYmivER/zpN5wJSz9VKuSwg==
X-Received: by 10.223.178.206 with SMTP id g72mr10944629wrd.135.1519010861686; Sun, 18 Feb 2018 19:27:41 -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 j17sm24960537wmc.41.2018.02.18.19.27.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Feb 2018 19:27:40 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <66C43C40-B24D-41E7-B59B-F26D2EE194A8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8FC6C9EF-5185-4B9B-A785-769C1B998256"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sun, 18 Feb 2018 19:27:38 -0800
In-Reply-To: <06602FE1-B3CA-477C-AD2F-ED6B6AB9F9A2@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, iasa20@ietf.org
To: Glenn Deen <rgd.ietf@gmail.com>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <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> <06602FE1-B3CA-477C-AD2F-ED6B6AB9F9A2@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/mPFsbDGnwJaqfNFY95JtBy74wxE>
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:27:44 -0000

Glenn,

> On Feb 17, 2018, at 12:42 PM, Glenn Deen <rgd.ietf@gmail.com> wrote:
> 
> 
>> On Feb 16, 2018, at 3:00 PM, Bob Hinden <bob.hinden@gmail.com> 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.
>> 
>> Bob
> 
> There are different degrees of independence as represented by the three models.
> 
> While financial independence comes with the real responsibility to live within our budgets and foundational moneys like any mature organization has to, it does permit donors to directly know that what they give to the IETF really grows the IETF budget and not simply offset money ISOC would have otherwise contributed were it not for the donation.

Yes, but only if ISOC then stops picking up a deficit too.  We can’t have it both ways.  Otherwise the donors will know that if they don’t give, ISOC will pick up the difference.

> 
> It may actually help us raise funds more easily in some circles.

I hope so.  However, I still think this is not the main reason we have trouble funding the IETF.  There are changes in the industry that have reduced the number of possible donors and many of the traditional donor's business is not growing.

Bob


> 
> Glenn Deen
>