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

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 19 February 2018 17:26 UTC

Return-Path: <ajs@anvilwalrusden.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 2B54A126C0F for <iasa20@ietfa.amsl.com>; Mon, 19 Feb 2018 09:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=A94IpQsC; dkim=pass (1024-bit key) header.d=yitter.info header.b=lNorRmRR
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 jmDfU5Mc3O5h for <iasa20@ietfa.amsl.com>; Mon, 19 Feb 2018 09:26:00 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3E581243F6 for <iasa20@ietf.org>; Mon, 19 Feb 2018 09:26:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 23A77BD351 for <iasa20@ietf.org>; Mon, 19 Feb 2018 17:26:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1519061160; bh=YM77uQ66jUwF7hE5vXnSGbFTEbgq23ZJAZeWQkOVTM8=; h=Date:From:To:Subject:In-Reply-To:From; b=A94IpQsCUK3eSgbseBJ+tqpTxJQSEEeNf0jBr+QHv6kNxPvJ9s2esIGS1d3pjLkfW PESmdNuyQahzRxZdQgvdzDk0e8NK7ENET1kZn0bfgaii4Pu3vG52Lczj4mODraJgX8 2OzoQ4K3udkIyT66iXc74Az2mVnCGYBAsTh9yukc=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHqm87-bUTOw for <iasa20@ietf.org>; Mon, 19 Feb 2018 17:25:58 +0000 (UTC)
Date: Mon, 19 Feb 2018 12:25:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1519061158; bh=YM77uQ66jUwF7hE5vXnSGbFTEbgq23ZJAZeWQkOVTM8=; h=Date:From:To:Subject:In-Reply-To:From; b=lNorRmRRt07PA5qVm8vY1OByJ4Fmb7UZjHa9Pvq99jlliRNpdrp8Sxaam5atyO98m H1+uiw4Cebp+TUvBTzNQkI/Y9OJ/K1hjV+FwmgGjJyDi1gXZF5oQ4w8TdJu3+2xWlV ostRLK40XynkULobJ95di4KLt9FWPoO+SdGOKy1o=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: iasa20@ietf.org
Message-ID: <20180219172558.nffdatzzc4pylz3f@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <66C43C40-B24D-41E7-B59B-F26D2EE194A8@gmail.com> <207946BC-85B2-4E4F-BCA4-A4452A3BADA1@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/pyirvE1vIR5KhH-EoIdrUGlwFLY>
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 17:26:02 -0000

On Sun, Feb 18, 2018 at 07:20:40PM -0800, Bob Hinden wrote:
> > 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.

I know how this works.  But we are talking to _donors_, not people who
are spending all their time looking at the details of our finances.
Simple consideration, if nothing else, ought to make us want to make
thinking about this psychically unburdensome, and right now people
have to think about the funding model and how we relate to ISOC and so
on.  That has been a consistent complaint of various donor people that
several of us have spoken to, and it has also been something that
people who work in sponsoring corporations have raised in the WG.  If
you are claiming all those people are wrong, the burden of proof is on
you.
 
> 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.
 
That is possibly true.

On Sun, Feb 18, 2018 at 07:27:38PM -0800, Bob Hinden wrote:
 
> I hope so.  However, I still think this is not the main reason we
> have trouble funding the IETF.

I don't think anyone has argued about what the "main reason" for
trouble funding the IETF is.  I think what people have said is that,
in their efforts in this area, this arrangement is problematic and has
been identified by potential donors as being problematic.  It seems to
me therefore that it is one of the criteria we should use to judge any
new arrangements: will it address this issue?

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com