Re: IETF funding needs (Was: Re: IETF Endowment update)
S Moonesamy <sm+ietf@elandsys.com> Wed, 13 July 2016 16:08 UTC
Return-Path: <sm@elandsys.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 4D9FD12D135 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2016 09:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.077
X-Spam-Level:
X-Spam-Status: No, score=-3.077 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=LnnJ2fc4; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=iZ4tNvto
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 HvlK9VJBrPJw for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2016 09:08:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C14212B00D for <ietf@ietf.org>; Wed, 13 Jul 2016 09:08:34 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.147.25]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u6DG8I8U009756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Jul 2016 09:08:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1468426112; x=1468512512; bh=n0D/i7YbR6W6NN4dE1BDlcta8nNyDXppWk3CbUvQZjI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LnnJ2fc4IbRzE8LDyqIx6FgWRruaDwCXabJSgo6ihrOMkCPXxwUtddULUOeULkwMo o/Sscr14vprgZmbzldyZdCDQjNIqvqYn49QKTH3PwVU7HPvbCBU7uhryKnX4eqWWaA Y+7ZpIZsjmWT8S8rfnPXRC5j1agyUZKEKx2E9Gvo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1468426112; x=1468512512; i=@elandsys.com; bh=n0D/i7YbR6W6NN4dE1BDlcta8nNyDXppWk3CbUvQZjI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iZ4tNvtoJDQE5BTc4MgHddtZQ47hx3RIuihFxHAAnmd1qNSn5qmBGM2zd7f2s9ppS fUsihW88x7ZtEzUYiffLK4kokwIGCba8j5w75g43ht+EZvM9VJqJNW58UORpsRbooT eR1VVRKuqbU7hG5rr4O+Eejo/zcSxioP8AcwlkCY=
Message-Id: <6.2.5.6.2.20160713072518.0bfc7808@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 Jul 2016 08:56:31 -0700
To: nalini.elkins@insidethestack.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF funding needs (Was: Re: IETF Endowment update)
In-Reply-To: <2055465314.2895150.1468391840392.JavaMail.yahoo@mail.yahoo .com>
References: <D3AA6473.17603E%brown@isoc.org> <4CFE92A053EFFCAC5A1EBF2C@JcK-HP8200> <B968F338-379C-44CC-A509-5B9B3DC14D09@piuha.net> <2055465314.2895150.1468391840392.JavaMail.yahoo@mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bMqLIB3K-iONBTFGhRLOiMqce98>
Cc: Kathy Brown <brown@isoc.org>, 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: Wed, 13 Jul 2016 16:08:35 -0000
Hi Nalini, At 23:37 12-07-2016, nalini.elkins@insidethestack.com wrote: >I think that funding, how to get more funding, and what to do with >it is one of the most important conversations that we could be having. [snip] >This is not so dissimilar to what happens at the IETF. If you work >for an organization which will send you consistently to IETF (or you >have access to adequate personal income) and if you can spend the >time out of your work week that is required to participate remotely, >then you can become involved and active. IMHO, it is MUCH harder >to be involved and to create the networks of contacts that are >required to create thoughtful protocol standards without physical >attendance. I know that some have done it. I am saying that for >most it is much harder. And, yes, some children manage to rise >above the impacts of poverty as well. Most don't. [snip] >My concern is with people who are not here and who maybe SHOULD be >here both for their own growth and eventual contributions and for >the perspective they can add to the conversations at the IETF which >are so important. The discussion is about the fourth point: "Evolve IETF sponsorship models to focus more on our work than meetings" and probably the first point: "Make it easier for people to be involved in the IETF". At the individual level there isn't a funding need if the company a person works for is already paying for a person to attend an IETF meeting. As a SDO, does it benefit the IETF to fund persons not covered in the previous sentence? The concern (see quoted text) mentions eventual contributions and for the perspective. Why is that so important now? For what it is worth, IETF participants, excluding one or more, did not support that in 2013. I am going to use some words that are overused: trade not aid. That approach is better than philanthropic funding. Regards, S. Moonesamy
- 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