Re: IETF Endowment update

<nalini.elkins@insidethestack.com> Sat, 16 July 2016 05:13 UTC

Return-Path: <nalini.elkins@insidethestack.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 64D8312D643 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 22:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 5XTDJwqOUAnk for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 22:13:37 -0700 (PDT)
Received: from nm21.bullet.mail.ne1.yahoo.com (nm21.bullet.mail.ne1.yahoo.com [98.138.90.84]) (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 9865612B01F for <ietf@ietf.org>; Fri, 15 Jul 2016 22:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1468646016; bh=8RMJPEjQTkN6129k+fJ/8eHJ8zJLUW0XZSnCh4BUKh0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=LbF65UeZDCDLmR/YOWOGW9pcfWEYCv7gee5uPT/vFVB7xHcfkeV1cQWSp69NHoTllQ4IvVqfIHFYr5LFWTqKNRE4TityveJOtyx46/QFyqD9F7wNBISFSdAB9i7gJvI1Q60kQ5c/Az5GB1CGoh54Njc7hmf9Z4qeGTYc/pY3SCm8jzqG2O5XC4z63vz4nXS+3WP00FA5XF0ztgGH/i2ApwUo04fPKTH8Chf5Mc8eOV3rXknWXKV/h+CxCA5D6hqH/eNFxdOXVWmP+2lQEIHnwxQXYoCEUuekZcQMRFVbAw4NIwnM71c+cMwjHJYfTfQpZIDQEmJOzqY8UbYo+/jlUg==
Received: from [98.138.101.131] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 16 Jul 2016 05:13:36 -0000
Received: from [98.138.226.161] by tm19.bullet.mail.ne1.yahoo.com with NNFMP; 16 Jul 2016 05:13:36 -0000
Received: from [127.0.0.1] by omp1062.mail.ne1.yahoo.com with NNFMP; 16 Jul 2016 05:13:36 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 918502.13612.bm@omp1062.mail.ne1.yahoo.com
X-YMail-OSG: Y5z22goVM1nSkFqXtG5F_V9YAMRzUIDC7gCvC05YIWihGpKb1GEAmrD7OuHVAI2 KRfptzZWgdMuQBk5CKn57Z0X4YhYQgEsQ3lyixdTeCmTRcvY3GYDsUwY.RiJOCfpFZBZkrMwl_Hs sach7esxZNP0yn84VzcVR2gmtHIc4FdyQOWIocu5Q_Uzn28Fkt4uWhvqKEn.xJ_oM91bxI_6Z2YE zw.sflQo2n05OlcvlmsIee2LppvWzgVxPpkNQwFmTez0SvyO3QIWo9pJw5M9hLpDe1rLTBMVL3ki HVu1FnAWieU4dHe4uDLM12NtZP_s29KywscG3vmLOgOz4TTrexD7SsxEfZdCKyeeNAPcpNg.IEZ5 m7cqpL6k27754Jv2vxO2DwTdse86KyuLCb7tSZfnTv26SlcYm_y3.tF8GC1GXcWx26nDmb2fTc7A buMRski8FJqbUIn8iYeC.5JCkQSIRO6rEU9lL2Urm3iHM66ASyvmoBlseBuU4qKiPvNu3uthnJaF NJwqop2fE0ekaznRiH5HtYMJxXVWGyBw-
Received: from jws10065.mail.ne1.yahoo.com by sendmailws162.mail.ne1.yahoo.com; Sat, 16 Jul 2016 05:13:36 +0000; 1468646016.469
Date: Sat, 16 Jul 2016 05:13:28 +0000
From: nalini.elkins@insidethestack.com
To: Phillip Hallam-Baker <phill@hallambaker.com>, Harald Alvestrand <harald@alvestrand.no>
Message-ID: <1006723510.109496.1468646008521.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAMm+Lwj=gA+ZPOgBR=-T1M8+L9MPZta-w6cevFR-Lk2re+cfzw@mail.gmail.com>
References: <20160715000647.41148.qmail@ary.lan> <44BE89E0-70F5-4CEC-B660-FEF90365AC4A@gmail.com> <0b11500e-9c21-c583-79f6-4cd33b0b9067@cisco.com> <5789429A.3070503@alvestrand.no> <CAMm+Lwj=gA+ZPOgBR=-T1M8+L9MPZta-w6cevFR-Lk2re+cfzw@mail.gmail.com>
Subject: Re: IETF Endowment update
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_109495_1298292432.1468646008509"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZDTqR3NJQdH-8x-grNVRcU-APP8>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Sat, 16 Jul 2016 05:13:39 -0000



>+1 to Harald's point.
+1 from me also and esp. to:
"The IETF needs to be the very opposite of timid going forward.  Reserves will help that."
What a great statement!  Thank you for saying that, Harald.
>I have been worrying that the conference fee model is a trap for quite a while. It is very similar to the 'innovators dilemma' problem.

I don't agree about the conference fee for most people but I do think that more (and other) people need to be subsidized.   How exactly we decide who gets subsidized is a different thread.   I think the conference fee is actually pretty cheap.  It is travel that is much more expensive.

>There is one other way round that could work and that is to adopt the Linux foundation model of giving paid courses to non experts. Which would in effect mean using the >IETF brand to go into the training business.

I have some other suggestions to make somewhat in line with Philip's suggestion for revenue generation.   I do very much agree with revenue generation.  I don't agree with doing training classes.   As someone who actually does training classes for money, it is more work than you might imagine.  
So, here are some ideas for revenue generation.
1.   What if IETF did small videos (maybe 10 minutes) on various topics?   These would be videos that only IETF COULD make.  Say for example:
- What was IETF 1 like?  
- How did IPv6 actually come about? (Or DHCP, DNS, etc)
- Why is NAT a "four letter word" at the IETF?
- What does "strong cryptography" really imply?
- Where is the Internet going?  (How did it get to where it is, etc)
You get the idea.
These videos could be just conversations with a few people involved.  No need to get caught up hugely with production quality.   A few steps above the normal cat video is probably fine.   Then you charge $5 or so for each video.   I would pay to watch these.   I am sure plenty of others would also.
So, OK, maybe 1,000 people watch each one.  Who knows, maybe more.  I can see that a number of teachers might want to use these in their classes.   So, IETF endowment gets $5,000 here, $10,000 there.  Why not?  I don't think it would take that much effort.  Over time, if it gets popular, there could be quite a bit of money earned.
BTW, I would be willing to help corral people to participate in such conversations, if ISOC needs IETF volunteers to work on such a project.  I assume it would be ISOC doing this.

2.  Maybe companies who send 10's or 100's of people to the IETF could subsidize one person for each 10 they send.   Even my little startup (when we had some extra money!) paid the conference fee for someone else at the Dallas IETF.   The person was local, so travel was not a problem.  
I know ISOC gets donations from companies but maybe this could become an unstated moral obligation of sorts.

3.  Often people leave charitable organizations money in their wills.    So, why not to the IETF endowment?

Thank you all who have donated to the endowment.    Maybe someone could send out the link again to where to donate.   Was there one?
Nalini
On Fri, Jul 15, 2016 at 4:07 PM, Harald Alvestrand <harald@alvestrand.no> wrote:

One of the things I've learned in dealing with budgets is that the size
of your reserves significantly influences the size of the risk you can
take - with any steering group with financial responsibility, they will
not take risks where the potential downside is larger than the reserves
of the organization.

This means that an organziation without reserves is, by necessity, a
timid organization.
Some of that can be mitigated by depending on other organizations'
reserves (like IETF depends on ISOC), but it's not necessarily a good
thing for either organizations to be in such a relationshiop.

The IETF needs to be the very opposite of timid going forward.
Reserves will help that.

I see the IETF Endowment as a means of making sure the IETF has the
reserves to take the risks it needs to take without asking our leaders
to abandon financial responsibility.

I'm proud to have my name on the list of sponsors.

Harald