Hi, On 7/15/16 7:09 AM, Suzanne Woolf wrote: > Thanks John— this is very close to one of my main reasons for supporting the endowment. +1. > > 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. Yes, but I haven't given up hope that we could actually arrange to have fewer plenary meetings, or at least have that experiment. > > 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. Yep. > > 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. Yep. It is possible to overfund an endowment, but at the moment that isn't our problem. Eliot
Attachment:
signature.asc
Description: OpenPGP digital signature