Re: IETF Endowment update
Richard Shockey <richard@shockey.us> Fri, 15 July 2016 20:57 UTC
Return-Path: <richard@shockey.us>
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 7731212D0F8 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 13:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 HT6Yi2R61mFi for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2016 13:57:19 -0700 (PDT)
Received: from gproxy10-pub.mail.unifiedlayer.com (gproxy10-pub.mail.unifiedlayer.com [69.89.20.226]) by ietfa.amsl.com (Postfix) with SMTP id 1F7C512D898 for <ietf@ietf.org>; Fri, 15 Jul 2016 13:57:18 -0700 (PDT)
Received: (qmail 12814 invoked by uid 0); 15 Jul 2016 20:57:15 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy10.mail.unifiedlayer.com with SMTP; 15 Jul 2016 20:57:15 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by cmgw3 with id K8xB1t00a1MNPNq018xExU; Fri, 15 Jul 2016 14:57:15 -0600
X-Authority-Analysis: v=2.1 cv=LOD1Hvm9 c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=8WrITzYgnNwA:10 a=iYKGedMQ2FkA:10 a=cAmyUtKerLwA:10 a=PeFO9FbFhS32YxYntvkA:9 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=48vgC7mUAAAA:8 a=WOIJDy4HAAAA:8 a=-XYu9_NAzIaCrGfvuY0A:9 a=QEXdDO2ut3YA:10 a=ivbTfD_dPm4A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=-JGFDwYPzB4B52txeMIA:9 a=4kZponavIrDXF8K9:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=VpyrLIdO_Ztbr3SWPBuH:22 a=6yl0mh0s51TKORVA8GqK:22 a=w1C3t2QeGrPiZgrLijVG:22 a=RH9Et_pqK2yyrEzRTb3T:22 a=BKKCjISod1eDJeS0ORpz:22 a=zjWhRoSqWz9hl55Hdlzg:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:CC: To:From:Subject:Date; bh=yvArawAjVj7hAel35rIWlGea4Dj4QF2gpujFwWWGy0A=; b=D03F 5AmEXxqtEhmGTJjobstOZkGP1CFFDoRz1/7c39Id/EzurmFiDUytHTsMQ+OWKP5CfpXNlXBS3jaPT E57UwcbYOZ4NHk7h7dJgWUsv7yFoBkm5V9R6Qo5kEd/Byns;
Received: from [31.133.143.179] (port=56457) by box462.bluehost.com with esmtpa (Exim 4.86_2) (envelope-from <richard@shockey.us>) id 1bOAAZ-0003cu-6x; Fri, 15 Jul 2016 14:57:11 -0600
User-Agent: Microsoft-MacOutlook/f.18.0.160709
Date: Fri, 15 Jul 2016 22:57:02 +0200
Subject: Re: IETF Endowment update
From: Richard Shockey <richard@shockey.us>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Harald Alvestrand <harald@alvestrand.no>
Message-ID: <70EA6724-904D-422C-A468-371549762EDA@shockey.us>
Thread-Topic: IETF Endowment update
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>
In-Reply-To: <CAMm+Lwj=gA+ZPOgBR=-T1M8+L9MPZta-w6cevFR-Lk2re+cfzw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3551468231_188560860"
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 31.133.143.179 authed with richard+shockey.us}
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box462.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-Source-IP: 31.133.143.179
X-Exim-ID: 1bOAAZ-0003cu-6x
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([31.133.143.179]) [31.133.143.179]:56457
X-Source-Auth: richard+shockey.us
X-Email-Count: 0
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z2Qv7ojqQR7T4WVdEQZ5EO4_DE0>
Cc: IETF Discussion Mailing List <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 20:57:21 -0000
Nahh… sell naming rights to protocols and WG’s. You can’t form a new WG until you can sell off the naming rights… there is a start. Rename TCP/IP to the “Alphabet” protocol. Lets see 20M over 15 years. SIP to the ATT/SIP protocol .. — Richard Shockey Shockey Consulting LLC Chairman of the Board SIP Forum www.shockey.us www.sipforum.org richard<at>shockey.us Skype-Linkedin-Facebook rshockey101 PSTN +1 703-593-2683 From: ietf <ietf-bounces@ietf.org> on behalf of Phillip Hallam-Baker <phill@hallambaker.com> Date: Friday, July 15, 2016 at 10:36 PM To: Harald Alvestrand <harald@alvestrand.no> Cc: IETF Discussion Mailing List <ietf@ietf.org> Subject: Re: IETF Endowment update +1 to Harald's point. 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. 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. But that isn't an entirely risk free proposition. The course material would have to be designed not to compete with other courses that companies participating in IETF provide, so no product training. And the other problem is that the reason training has insane margins is that it hits a wall and goes to $0 when a recession hits. What is clear is that the current approach isn't sustainable. We are making many modes of working obsolete including the way the IETF does business. Ooops. 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
- Re: IETF Endowment update Leif Johansson
- Re: IETF Endowment update nalini.elkins
- Re: IETF Endowment update Ole Jacobsen
- Re: IETF Endowment update nalini.elkins
- Re: IETF Endowment update Richard Shockey
- Re: IETF Endowment update Doug Ewell
- Re: IETF Endowment update Scott O. Bradner
- Re: IETF Endowment update Richard Shockey
- Re: IETF Endowment update Phillip Hallam-Baker
- Re: IETF Endowment update Harald Alvestrand
- Re: IETF Endowment update Eliot Lear
- Re: IETF Endowment update Suzanne Woolf
- Re: IETF Endowment update John Levine
- Re: IETF Endowment update Kathy Brown
- Re: IETF Endowment update Michael StJohns
- Re: IETF Endowment update Livingood, Jason
- Re: IETF Endowment update Paul Wouters
- Re: IETF Endowment update John C Klensin
- Re: IETF Endowment update Kathy Brown
- Re: IETF Endowment update Richard Shockey
- Re: IETF funding needs (Was: Re: IETF Endowment u… S Moonesamy
- Re: IETF funding needs (Was: Re: IETF Endowment u… nalini.elkins
- IETF funding needs (Was: Re: IETF Endowment updat… Jari Arkko
- Re: IETF Endowment update John C Klensin
- IETF Endowment update Kathy Brown
- Re: IETF Endowment update Paul Wouters
- Re: IETF Endowment update Russ Housley