Re: Remote participation fees [Re: Updating BCP 10 -- NomCom ELEGIBILITY]

John C Klensin <> Sat, 14 February 2015 18:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4007C1A0037 for <>; Sat, 14 Feb 2015 10:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.21
X-Spam-Status: No, score=-1.21 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iEzG2kUqmDa6 for <>; Sat, 14 Feb 2015 10:14:51 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E36581A0015 for <>; Sat, 14 Feb 2015 10:14:50 -0800 (PST)
Received: from [] ( by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1YMhEi-000BIb-9S; Sat, 14 Feb 2015 13:14:36 -0500
Date: Sat, 14 Feb 2015 13:14:31 -0500
From: John C Klensin <>
To: Yoav Nir <>
Subject: Re: Remote participation fees [Re: Updating BCP 10 -- NomCom ELEGIBILITY]
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Cc: ietf <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 14 Feb 2015 18:14:54 -0000

--On Saturday, February 14, 2015 18:43 +0200 Yoav Nir
<> wrote:

> Also, supporting remote participation in a better way than it
> works today costs more money than is being expended today.
> That money has to come from somewhere.

As a periodic remote participant, some observations:

First, the big costs to me of a f2f meetin are associated with
being away from home, getting on airplanes (for some medical
reasons, especially bad news when the meeting is outside North
America) and staying in a hotel.  The registration fees have
crept up well beyond the historical nuisance and cookie charge,
but are still close to the noise of overall expenses.

Second, I would actually prefer to be formally registered and
paying some reasonable remote participate registration fee.  I'm
prefer to be recorded as attending sessions I attend and
participate in, whether by my name going on the blue sheet with
an asterisk or by some other mechanism.  I don't like the idea
of others (or even their companies) subsidizing me and would
prefer to be in a situation in which there were established
conventions about what, as a remote participant, I have the
right to expect.  In general, people have been _very_ good about
it, but, when the audio isn't working for the first session on
Monday morning (from my observations, a common problem) I
believe that I, and remote participants who are more shy about
complaining than I am, should feel that we are entitled to have
that situation treated as a major, probably session-stopping,
problem, on a par with the in-room lights or projector not
working or no one in the room being able to hear a speaker.
Similar comments apply to not being able to make a comment or
ask a question during a meeting because of the way the
microphone lines are being managed.

Now I do think that having some fee waiver systems for hardships
is important, but actually no more important than having similar
arrangements for hardship waivers for in-person attendees.  And
I don't think people who just want to listen (or watch) remotely
should be charged or asked to identify themselves as the price
for doing so.   Nothing prevents someone who doesn't way to pay
the fee or ask from a waiver fro listening and then taking
issues up on the relevant mailing list either.  But, if nothing
else, in the interest of openness and fairness, those who are
_participating_ remotely ought to be registered (like everyone
else), identified as participating in specific WG sessions when
they do so (like everyone else), and that it is entirely
reasonable that there be a corresponding registration fee (as
for everyone else).