Re: IETF Endowment update

Suzanne Woolf <suzworldwide@gmail.com> Fri, 15 July 2016 05:09 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8088812D7EF for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2016 22:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 gXEt4jd3zV5D for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2016 22:09:34 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 2A6CE12D626 for <ietf@ietf.org>; Thu, 14 Jul 2016 22:09:32 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id f65so11674921wmi.0 for <ietf@ietf.org>; Thu, 14 Jul 2016 22:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ukFpUrAosdfM+riLV3nb+FTtC3Go0M9aZd7GNT7bAfQ=; b=O04C9qOcSQaW2EC9EEk6oBUiOUCk//2jG9uAiN8C+wzlMRsOFTtajh8AESge9e2H+8 UGBQas0mATqdXye/SV+I1D7P3oD/7ps3TpLxYizKdatR/xPX510etrC019Ln19+TcxzQ /GKhr0W+U9xOY0gtGGRLtyt8vYbpzs9eIIX+eA/Q129VBTUOSuNd3VkQLknapCpQnayA PFmt3R0TDH1rI/rGNSGhanqXGSWoEIAmYPnl8FmWdSkOGnDzdudve9lIsyUr/6zwtnwt AUp7I2sXRvAejOrQBXrXAbt+868nzQYp1BernuldyCwmOdmwKLSowcPSgzSmpY3RZk/6 o8uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ukFpUrAosdfM+riLV3nb+FTtC3Go0M9aZd7GNT7bAfQ=; b=Zp9kqvzJtWexkjL5SV8Ge6kVz3y1caJorlEeqDR5FDmqUcJKfsk/w8SLUlS6RK5GUn Tu/qUaVvPXHa4aGPYDRhUBFZpB4qkz2ELesyIYSk3CSlpBMMqXbtYtE5oBo7u7JwqDtz YK1AYIigi6byRJEb7+qwtWiVXaccqvTak/+lCYMEANDz0G9iXLoO6z1qHybCssb7HOTR 4ilSSGZfApAUM868n0JEfXbdmB2oRPRDCPuZ0Gd8EqlPSnqE6mXkcJHl85C1TvwURCJO LbVLP3UlIntturhp1rRh6x9p3qYq/Hthfr1Hu/iw+A3G5HTm8KV+G60+QA/RSvqW/EfV Wcxw==
X-Gm-Message-State: ALyK8tJnxbl2/YicF273sWkeVFkO7RQxhtYJU+ZnCf8AqSDEnG4wyPc3S3gbS3h4Omb92g==
X-Received: by 10.28.63.214 with SMTP id m205mr19387261wma.72.1468559370645; Thu, 14 Jul 2016 22:09:30 -0700 (PDT)
Received: from [10.53.146.177] ([88.128.80.50]) by smtp.gmail.com with ESMTPSA id i66sm2858101wmg.9.2016.07.14.22.09.29 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 14 Jul 2016 22:09:29 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: IETF Endowment update
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20160715000647.41148.qmail@ary.lan>
Date: Fri, 15 Jul 2016 01:09:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <44BE89E0-70F5-4CEC-B660-FEF90365AC4A@gmail.com>
References: <20160715000647.41148.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KP45f1VEep-1qGtDWF7xSFkpKjY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2016 05:09:35 -0000

Hi,

> On Jul 14, 2016, at 8:06 PM, John Levine <johnl@taugh.com> wrote:
> 
>> Regarding the concern that John Klensin raised about Internet organizations that have too much money, I
>> cannot imagine this endowmwnr being that successful.  However, if it were, I would argue for reduced
>> meeting fees to encourage the broadest possible participation in face-to-face meetings.
> 
> The IETF gets about 1/3 of its income from meeting fees.  If, as seems
> likely, we have more people coming electronically and fewer in person,
> we're going to need to replace the revenue since to a first
> approximation if we meet in person at all the costs are independent of
> the number of people that show up.  So either there's a death spiral
> of in-person meeting fees, we try to charge people who attend
> remotely, or we find the money somewhere else.  I see this as the
> obvious candidate for somewhere else.

Thanks John— this is very close to one of my main reasons for supporting the endowment. 

If we want to support diversity of participation and input to the IETF, we can’t do it only by having an ever-longer list of places where we have physical meetings. It’s expensive in many ways— time, money, tradeoffs among multiple values we care about. The pressures to clarify and evolve how we handle outreach, diversity, venue selection, and other aspects of making the IETF look like “the internet” are important. But I do think a sustainable IETF has to get better at the tools and practices to do distributed work more effectively.

Working group chairs, the tools team, the secretariat, and everyone else involved in making this whole endeavor go— which is to say all of us— are putting a lot of effort into such improvements. IMO we’ve got the will to do it. But it’s also going to cost money to get better at it— and getting better at it may, as John points out, also undercut the current funding sources.

In short— if we’re going to get better at distributed work, and cope effectively with the pressures on the IETF to change the purposes and priorities for its physical meetings, it seems to me that we need to separate our funding model from our ability to implement new working methods.

My other reason for supporting the endowment is a more philosophical one. For any organization, diversity of funding sources is good. Currently the IETF is significantly dependent on one organization (ISOC) and one industry (domain names). Some avenues to funding that other SDOs use aren’t really open to us— on principle if nothing else: for example, an endowment may be controversial, but I’d expect (and hope!) that charging for RFCs would be a complete non-starter.

Helping to assure diverse funding for the IETF is another way in which ISOC has helped the IETF and will continue to do so. Thank you Kathy and the ISOC Board.


Suzanne
(speaking for myself)