IETF Logo Mail Archive

Re: IETF Endowment update

Harald Alvestrand <harald@alvestrand.no> Fri, 15 July 2016 20:08 UTC

Return-Path: <harald@alvestrand.no>
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 21A2912DDCA for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 13:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
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 k-cjVUKIfc9e for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 13:08:33 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F58112DD8C for <ietf@ietf.org>; Fri, 15 Jul 2016 13:08:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 276B27C8BB0 for <ietf@ietf.org>; Fri, 15 Jul 2016 22:08:02 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ui2LHzNPudAk for <ietf@ietf.org>; Fri, 15 Jul 2016 22:08:01 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:1:7d18:6055:f9e:ec59] (unknown [IPv6:2001:470:de0a:1:7d18:6055:f9e:ec59]) by mork.alvestrand.no (Postfix) with ESMTPSA id 6714E7C8BAD for <ietf@ietf.org>; Fri, 15 Jul 2016 22:08:01 +0200 (CEST)
Subject: Re: IETF Endowment update
To: ietf@ietf.org
References: <20160715000647.41148.qmail@ary.lan> <44BE89E0-70F5-4CEC-B660-FEF90365AC4A@gmail.com> <0b11500e-9c21-c583-79f6-4cd33b0b9067@cisco.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <5789429A.3070503@alvestrand.no>
Date: Fri, 15 Jul 2016 22:07:54 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <0b11500e-9c21-c583-79f6-4cd33b0b9067@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="FUtRq82USLeKMvD2RbeWkCbFLvxwIxO26"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NsMWmND38oXIbeESCykCMmh_jcw>
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 20:08:35 -0000

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

v2.23.0 | Report a Bug | By Email