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

Mary Barnes <mary.h.barnes@gmail.com> Sat, 14 February 2015 22:46 UTC

Return-Path: <mary.h.barnes@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 1D1711A0267 for <ietf@ietfa.amsl.com>; Sat, 14 Feb 2015 14:46:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 v9oe8B6e08Cd for <ietf@ietfa.amsl.com>; Sat, 14 Feb 2015 14:46:50 -0800 (PST)
Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) (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 615DD1A01D8 for <ietf@ietf.org>; Sat, 14 Feb 2015 14:46:49 -0800 (PST)
Received: by labhz20 with SMTP id hz20so22343442lab.0 for <ietf@ietf.org>; Sat, 14 Feb 2015 14:46:48 -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=pLR/+Pug1yS1xxAVD+O0NPMtzZtYCOOBhCLkFq74da4=; b=FmDJvqZdjosMNC7uzlk4xBHjn1GKoSeLxkpi6coHbqIkEXfaTD9dOXCdj2EZLvhe+T Xp65xAgADJkCafLmnWPwOm//FKaxVciT7Qq13AnPnc6hhEoKyISnoeQB/2HQuk8BBu/C rwtwjOkJlimCCNop8lYrIRS7F0gd2DxLzkMX96Q82qVP4P4wE8VGRDhvoLg6HpIBaY6r +H10n53hV4cx+FHkOKQP/5Y9sFvHKJlpUs14yRfREOtw11LGneta3ac/r2jjbl3Wghqe gS7ZV8RxRoLfbUJe6O+caQ/lC9KLofl2jJPANJMI/AfNvJwtO+hzM/g1agr/twvPL/QV aTpA==
MIME-Version: 1.0
X-Received: by 10.152.18.133 with SMTP id w5mr14755688lad.51.1423954007917; Sat, 14 Feb 2015 14:46:47 -0800 (PST)
Received: by 10.25.40.133 with HTTP; Sat, 14 Feb 2015 14:46:47 -0800 (PST)
In-Reply-To: <12AEC0C5AEA44D6E886E6E21@JcK-HP8200.jck.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@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> <12AEC0C5AEA44D6E886E6E21@JcK-HP8200.jck.com>
Date: Sat, 14 Feb 2015 16:46:47 -0600
Message-ID: <CABmDk8mC6rpwrhhM0ySY8wkGjsjX-1eerw30EpQeN6aJpQgAFw@mail.gmail.com>
Subject: Re: Remote participation fees [Re: Updating BCP 10 -- NomCom ELEGIBILITY]
From: Mary Barnes <mary.h.barnes@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e01493d40d18ad6050f14202d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2ZajM8e1i726LaGKs8JpcOiHbuk>
Cc: ietf <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: Sat, 14 Feb 2015 22:46:53 -0000

Rather than respond inline, I'll respond generally as I personally haven't
gone down the road towards looking at the impacts
which rightly should be considered.   I'm not saying improving remote
participation is just a piece of cake and there
are no barriers to doing so.  I'm just suggesting it be a consideration and
not be tossed aside or be given
low priority  just because some folks are concerned about the impact on
"IETF culture" and the financial bottom line.

Regards,
Mary.

On Sat, Feb 14, 2015 at 3:16 PM, John C Klensin <john-ietf@jck.com>; wrote:

>
>
> --On Saturday, February 14, 2015 12:21 -0600 Mary Barnes
> <mary.h.barnes@gmail.com>; wrote:
>
> > [MB] True. But, perhaps considering other sorts of conference
> > facilities with nearby hotels could be an option.  In
> > particular, if we really do improve remote participation to
> > the point that we reduce the number of onsite participants,
> > the size requirement for the conference facilities goes down.
> > [/MB]
>
> Yes and no.  I haven't done site selections or evaluations for
> large meetings in many years but, unless things have changed
> significantly, the number of bigger-than-a-suite rooms we now
> seem to "need" (IAB office, IESG office, IAOC office, a Nomcom
> office and meeting room, an ISOC office or two, Secretariat work
> space, terminal room, NOC, ...) could turn into as much a
> barrier to moving to a smaller or less pretentious HQ hotel as
> the required number and size of WG and plenary spaces.
>
> >> 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.
> >>
> > [MB] In one sense yes. But, given some of the work in RAI,
> > this cost should be going down.  The ability to participate in
> > a meeting remotely with a very rich multimedia experience is
> >...
>
> Yes, but there is an issue that more and fancier protocols
> and/or hardware doesn't solve, which is that running these
> things well and at high quality tends to need serious
> operational commitments, which means more staff.  One can reduce
> the staff requirement somewhat with _really_ fancy and expensive
> technology, but the tradeoff may not be wonderful.  I'm not
> talking about the complex technical stuff here, I'm talking
> about things closer to "camera gives good view of carpet" and
> "if that speaker is going to pace the floor while talking,
> either the camera needs to follow or someone needs to apply a
> short leash" to say nothing of the perennial microphone
> announcement, "MY NAME IS <mumble>".
>
> Similarly, very high quality remote participation with lots of
> participants at lots of different locations tends to either put
> a premium on participant training and/or typing speed and/or a
> requirement for trained moderators who can control both in-room
> and remote conversation flow.  Again, not really technical
> issues, but not so easy to resolve, at least without cultural
> changes.
>
> > I think the biggest problem that high quality remote
> > participation will introduce is that companies will become
> > even more reluctant to send people to the face to face
> > meetings.
>
> Yes, although, borrowing from other threads, the proportion of
> design-level people to professional standardizers might start to
> improve again if participation didn't require members of the
> former group to give up whole days or a whole week.  Of course,
> that also has disadvantages in terms of competent cross-area
> review.  Not simple.
>
> >  I do still see value in people attending face to
> > face IETF meetings with some regularity, I strongly believe
> > that IETF moving to a model that doesn't require so many
> > people to travel to get the work done is a good thing and
> > ought to be a longterm objective.  I'm not a financial expert
> > so I can't posit that this will make sense from a business
> > model, but IETF is a non-profit and in that respect doing the
> > right thing for the community should be the overarching
> > objective.   [/MB]
>
> Again, be careful what you wish for, lest trying to optimize for
> people attending face to face meetings while not requiring so
> much travel, bring a situation in which almost all of the people
> at a meeting in Region X are from Region X, almost all of those
> at a meeting in Region Y are from Region Y, etc.  That loss of
> diversity in individual f2f meetings, even if it improved
> statistical diversity over a year or two, would not, IMO, be a
> desirable outcome.
>
>     john
>
>
>
>
>
>