Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details

John C Klensin <john-ietf@jck.com> Thu, 31 March 2016 18:39 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD8C612D6AD; Thu, 31 Mar 2016 11:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 0vsH5zsUSZyD; Thu, 31 Mar 2016 11:39:51 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86E5112D5AB; Thu, 31 Mar 2016 11:39:51 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1alhVW-0004cp-6l; Thu, 31 Mar 2016 14:39:50 -0400
Date: Thu, 31 Mar 2016 14:39:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, IETF Secretariat <ietf-secretariat@ietf.org>
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
Message-ID: <EC3639E5227509FD8106F471@JcK-HP8200.jck.com>
In-Reply-To: <56FD6B10.6050907@dcrocker.net>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <3B8E9BB3EC165D1102AA9714@JcK-HP8200.jck.com> <56FD6B10.6050907@dcrocker.net>
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-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZVzklbC6EWU0GNSddtTbUGsFar4>
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 31 Mar 2016 18:39:53 -0000


--On Thursday, March 31, 2016 11:23 -0700 Dave Crocker
<dhc@dcrocker.net>; wrote:

> On 3/31/2016 11:15 AM, John C Klensin wrote:
>> I notice that the placeholder for IETF 95 "Remote
>> Participation" athttp://www.ietf.org/  still is not
>> associated with a link.  On the meeting page
>> (http://www.ietf.org/meeting/95/index.html),
> ...
> 
> 
> Yes, there are some hiccups in some of the pages.
> 
> However I latched onto the directive that remote participants
> need to register and, after searching and finding the problems
> you cited, decided to try to register.  There I found that I
> could choose 'remote participation' as a class of registration
> and everything else was normal, except that it didn't charge
> me.

Yes, I found that too (and mentioned it in my note).   My
concern (independent of concerns about how the decisions were
made) is that you and I are about as experienced IETF old hands
(complete with appropriately-colored beards) as members of any
group of people around here.   A newcomer who can be easily
discouraged (rather than one who is exceptionally persistent and
determined) might well just give up instead.   I presume (and
hope) that is not the behavior we want to encourage.  

It really wouldn't take much effort to put a few sentences on
the meeting page (and either on the IETF home page or at the top
of the registration one) to say something like 'The IETF is now
requiring that remote participants register for the meeting
using the normal registration process but checking the new
"Remote Participant" category.  Doing so will give such
participants access to various capabilities including the
Meetecho remote conferencing system.'.   I'm just having trouble
understanding why it apparently didn't occur to anyone to do
that whether you and I can figure out how to navigate the system
or not.

   john