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

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 27 February 2015 05:12 UTC

Return-Path: <abdussalambaryun@gmail.com>
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 8761D1A3BA4; Thu, 26 Feb 2015 21:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level:
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 jqc8a1T-jGJY; Thu, 26 Feb 2015 21:12:21 -0800 (PST)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F171A3BA6; Thu, 26 Feb 2015 21:12:21 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id x12so11268402qac.13; Thu, 26 Feb 2015 21:12:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XwMgb9462M1rIrkV7rkgb18FrHQZetV6pOOYe9O4GOE=; b=UUwZaQ0/SiPUhBWylw9zKTj9AwQATHbE2tBA9w3dfb/LlAyqMo8g0nn4APVrJKnwZd hC8wRvDwuEprA3PhSRi3ilubMswgv5MxHx50+qcexjmTpk/r//u3hivo96Prt/LO8JyU OnBroFqWxogtjzYn1CGBqrcjEGKZ2sjJdAp4gW13wh76VH2+ZMqP+1GBz+ut64IA3mGQ +OZFCdJK1fNXjMemXjGoQ/UBX6F1Y7JA13UFuEUjWPWzkA6N8zsuIhTHzQ1X9FCL8+f8 mS83t0ctDeLVhNGaQBv9KiO2/FhoWI8ASqDVANB5V7vxEvrRLJ0Bjw1DfAPLCa8XwhhB ghHg==
MIME-Version: 1.0
X-Received: by 10.229.182.9 with SMTP id ca9mr26033681qcb.31.1425013940166; Thu, 26 Feb 2015 21:12:20 -0800 (PST)
Received: by 10.140.108.183 with HTTP; Thu, 26 Feb 2015 21:12:20 -0800 (PST)
In-Reply-To: <378E7F5B-3CFB-4F7D-B174-3D58A6451A15@standardstrack.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <6025.1423672358@sandelman.ca> <CAL0qLwYtE618sA99hgXP-5wk+BYdcXLbiZqd_36OreYQ1LB7hQ@mail.gmail.com> <54DBD71C.20101@joelhalpern.com> <26803.1423772214@sandelman.ca> <tsla90ikh85.fsf@mit.edu> <37661D4B-1842-4890-88FB-2A7B13CDC884@nominum.com> <CABmDk8m1KuSs8os9V7fcYOJC2O4yMb6dRFer+nEPBTTSHtey9Q@mail.gmail.com> <31891031-4628-49CD-B66C-38A3BD787B70@trammell.ch> <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> <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>
Date: Thu, 26 Feb 2015 21:12:20 -0800
Message-ID: <CADnDZ8-s6anrJhvg1RSf1FFqcfHY9SEOT-xgHCSyh48Rct9aVQ@mail.gmail.com>
Subject: Re: 'Paywall, ' IETF self-sufficiency, increasing participation (was Re: Remote participation fees)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Eric Burger <eburger-l@standardstrack.com>
Content-Type: multipart/alternative; boundary=001a1134546cb4280905100ae94c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BTkayBrn_iLP5t7pXev9ZEiEXzY>
Cc: "diversity@ietf.org" <diversity@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Fri, 27 Feb 2015 05:12:24 -0000

Thanks. IMHO participants  in IETF are in two categories: individuals and
companies, both needs to have diversity. I think IETF has shortage in
remote participants and in diversity, so the strategy is that no fees
because IETF needs more diversity.

However, the issue in my thoughts is not remote or non-remote or ability to
pay or not (diversity items), but the issue can be about benefits, cost and
payment return/outcome. For example, usually remote participants attend but
the outcome is less than others. In business and organisation what matters
is utilization of time, money, and attendance. People in business meet for
many reasons and different methods. All IETF participants attending meeting
physically have different utilization but pay the same fee. I think that
makes limited attendance. Now days Internet services changing to you pay
for what you use only, so could IETF offer that?

Let us focus on participant outcome (individual or organisation) from the
IETF meeting and then think about the fees to be added or increased per
category. IETF may need to look into that to manage participants'
satisfactions and expectations. I think companies that use and benefit from
IETF services should not be treated similar to individual participant. I
suggest that companies participating (i.e. company name is written in the
WG draft) should/may pay fees specific for that session utilization of
IETF.

AB

IETF Participant from Africa

On Wednesday, February 25, 2015, Eric Burger <eburger-l@standardstrack.com>
wrote:

> Mea culpa!
>
> My fault for not being articulate. I was responding to the discussion
> thread, and happened to chose this one to staple the reply to. I in no way
> meant to infer that Ted (or Dave or anyone else) was advocating that the
> IETF should be excluding people. In this case, the impression (which Ted
> pointed out to me) was that I was saying that he wanted to exclude people
> based on ability to pay. Ted and I discussed this off-list, and we are in
> violent agreement. I did not think he was advocating for that, and I do not
> want anyone to advocate for that.
>
> 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 Internet Society Trustee) would
> treat such a request sympathetically.
>
> I can see this could be a dynamic situation. I can envision a time when we
> as the IETF are truly successful and develop fantastic real-time
> communication protocols that are easy to deploy, cost almost nothing, and
> are secure. At that point, one would *hope* in-person IETF meetings become
> a relic of history. Maybe we would meet once per year or every other year
> to reminisce about how the only way to get work done was to spend thousands
> of dollars of cash per year and an uncountable amount of cost for travel
> time to physically meet in the same location. How 20th Century! At that
> point, I would expect surpluses from meeting fees would be nonexistent, and
> we would need to figure alternate means of funding. However, that day seems
> to be far enough away that charging for remote participation should be a
> remote possibility for the foreseeable future.
>
> > On Feb 24, 2015, at 9:24 PM, Ted Lemon <Ted.Lemon@nominum.com
> <javascript:;>> wrote:
> >
> > On Feb 24, 2015, at 8:32 PM, Eric Burger <eburger@standardstrack.com
> <javascript:;>> wrote:
> >> The last thing we need as we are just beginning to have success
> reaching out beyond North American, European, Japanese, S. Korean, and
> Australian mid-size to large corporations is to toss up a paywall, some as
> much as a month’s salary or more, for the ‘privilege’ of contributing to
> the IETF.
> >
> > You know, it's really frustrating when you participate in a discussion,
> try to contribute helpfully, and then essentially get accused of being a
> blithering idiot by someone who didn't bother to consider the possibility
> that you might not be.   I'm sure you've had that experience too.   Heck,
> I've been the one who assumed the other person was an idiot too, so I can
> relate.
> >
> > Anyway, if you think I was proposing a paywall, please go back and
> re-read what I actually wrote, and the rest of the discussion that
> followed, with the presumption in mind that I did _not_ mean to propose any
> such thing (because I didn't!), and see if the discussion still works, or
> if you find something I or someone else said that contradicts that
> assumption.
> >
> > Thanks.
> >
>
>