Re: 'Paywall, ' IETF self-sufficiency, increasing participation (was Re: Remote participation fees)

Dave Crocker <dhc@dcrocker.net> Wed, 25 February 2015 16:10 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9761A1AA4 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 08:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 ZlkMBiJlFgqt for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 08:10:37 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D2E51A6FCB for <ietf@ietf.org>; Wed, 25 Feb 2015 08:10:37 -0800 (PST)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t1PGAXO6029545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 25 Feb 2015 08:10:36 -0800
Message-ID: <54EDF3F4.6010000@dcrocker.net>
Date: Wed, 25 Feb 2015 08:10:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Eric Burger <eburger-l@standardstrack.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: 'Paywall, ' IETF self-sufficiency, increasing participation (was Re: Remote participation fees)
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <54DE7F09.8030500@gmail.com> <C5FC0DB6-82F8-4C38-ABFD-D5D9A6E65933@isoc.org.ec> <54DE90C6.6030609@gmail.com> <E39AF4E0-58AB-4249-8A37-3D1CD2D5A691@gmail.com> <54DE9844.1010807@gmail.com> <61FBB27B-4EF3-40A0-8981-00EB89698295@isoc.org.ec> <B90F5E29-06C5-41D1-9F31-1BE42382995F@gmail.com> <CABmDk8=YPZ1W2tTOqP23U2PFVLoDh-3+wwmcA8mpta-Y05op2A@mail.gmail.com> <54DFBAF6.30409@cs.tcd.ie> <m2h9uokmij.wl%randy@psg.com> <CE39F90A45FF0C49A1EA229FC9899B0525F9E295@USCLES544.agna.amgreetings.com> <1A71F670-BACB-485F-8F06-93720563CB9B@kitterman.com> <CAKHUC zwdzsnK H KGcR_-sxvJa1V6Ky9RXJdF179r6gRPWmAayVA@mail.gmail.com> <5D2D7FD3-B9C6-4BD3-BBEE-B2354EFC9996@nominum.com> <CAKHUCzxrLKNSTMYyt1BGO22MbsKtU2NfDvyLEpTZDnudaqgP=w@mail.gmail.com> <10863B07-6E63-470E-A9D8-67FA37A2097C@standardstrack.com> <287EAD95-42D4-449C-8A7C-E8B3A14C8C21@nominum.com> <378E7F5B-3CFB-4F7D-B174-3D58A6451A15@standardstrack.com>
In-Reply-To: <378E7F5B-3CFB-4F7D-B174-3D58A6451A15@standardstrack.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 25 Feb 2015 08:10:37 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-I9fYcJLljaGrFyk1PJAV52FH2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2015 16:10:39 -0000

On 2/25/2015 6:10 AM, Eric Burger wrote:
> Moving forward, what I was hoping to avoid was for people to think that because the IETF conference fees defer the costs of operating the IETF (the meeting itself, the secretariat, and a portion of the RFC Editor), that we have to try to squeeze every penny from all sources. That is not necessarily a bad mindset to have: we should be striving to be independent on the largesse of the Internet Society and their contributors if we can manage it. That is not an infinite pot of cash, and no one wants to be beholden to a single funding source. However, what I wanted to get out to the community is the message that the Internet Society believes deeply in expanding access to the IETF and the IETF process. If charging for remote access inhibits participation (the unfortunate ‘paywall’ comment), then I would have no problem at all suggesting the IETF (IAOC in specific) ask the Internet Society to fund remote participation. I think the Board (speaking as an individual, NOT in my role !
 as an In
ternet Society Trustee) would treat such a request sympathetically.

(To achieve a sufficiently broad base of funding that our loss of any
single source of revenue is tolerable would be particularly healthy.
However there really is nothing concrete in the IETF's current efforts
that will move us in that direction.  Some statements of desire, but
nothing that looks like an orchestrated plan or even a consistent
direction.)

Note that our current participation model is:

  Free:  Email list discussion.
         Remote attendance, with poor-to-mediocre access

  Pay:   IETF Meeting f2f Attendance

What's being discussed here is presumably far better remote attendance
capabilities.

As it approaches adequacy as a replacement for the basic uses of f2f
meeting attendance, it's not automatically clear that it should be
excluded from having a fee.  And I say that in spite of my continuing
concern that the IETF effectively restrict serious participation by
those with constrained budgets (and/or time.)

We already have a model with a free/pay range of participation.  If we
consider the model independent of technical details, we might find
choices that make sense but still have charging for at least some forms
of remote attendance or at least some remote attendees.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net