Re: Remote Participation for IETF 95: Meetecho Details

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 31 March 2016 06:12 UTC

Return-Path: <alexandre.petrescu@gmail.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 5E94112D0F4 for <ietf@ietfa.amsl.com>; Wed, 30 Mar 2016 23:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level:
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 rwkMVNgKq4y6 for <ietf@ietfa.amsl.com>; Wed, 30 Mar 2016 23:12:39 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7BA712D1BE for <ietf@ietf.org>; Wed, 30 Mar 2016 23:12:38 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u2V6CaKE002771 for <ietf@ietf.org>; Thu, 31 Mar 2016 08:12:36 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 68062201D91 for <ietf@ietf.org>; Thu, 31 Mar 2016 08:13:36 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5F0C220120D for <ietf@ietf.org>; Thu, 31 Mar 2016 08:13:36 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u2V6CaUf017482 for <ietf@ietf.org>; Thu, 31 Mar 2016 08:12:36 +0200
Subject: Re: Remote Participation for IETF 95: Meetecho Details
To: ietf@ietf.org
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56FCBFD3.7080804@gmail.com>
Date: Thu, 31 Mar 2016 08:12:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160330202243.4795.63685.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dZMYxZ0xy4YxRw16ZvGM8U_J6mk>
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 06:12:41 -0000

Dear IETF Secretariat,

Tools for remote participation are very necessary - thank you.

But I have one comment:

Le 30/03/2016 22:22, IETF Secretariat a écrit :
> You may use Meetecho to participate in or just observe any session
> being held in Buenos Aires. Here are the requirements and details.
>
> 1. Individuals are required to register for the meeting to observe or
> participate via Meetecho. - Individuals are required to enter
> registration I.D and name when logging into a session via Meetecho -
> The name must match that used to register for the meeting - Please
> register even if you are participating as part of remote hub - There
> is no cost to register as a remote attendee. Register
> here:http://ietf.org/meeting/register.html.
>
> 2. Participation includes the ability to transmit audio and video via
> the Meetecho virtual queue. - The virtual queue permits remote
> attendees to share audio and video if they choose, see here for more
> information:
> https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project

thanks, this is new and specific to IETF.

> - Anyone who thinks they may want to participate by transmitting
> audio / video should perform the Meetecho self-test prior to the
> start of the session:
> http://ietf95.conf.meetecho.com/index.php/Self_Test

That URL seems to be working only starting Saturday, it does not work 
now.  This self-test should not be announced now, unless it works now.

Second, the remote attendees should have a means to self-test even if
they just want to listen (not necessarily transmit audio/video).
Because, even if the in-browser webrtc tools claim there is nothing to 
install sometimes there is the browser itself, or the java to install or 
some plugins to approve.  In enterprise environments often these actions 
are blocked by security policy.  Because of that one needs time in 
advance to test and obtain derrogation.  Especially for session of 
Monday morning 9am.  Not everybody works during weekends, especially if 
remote (not at IETF).

Meetecho is a new tool for many non-IETFers and one doesnt want them go
to their other preferred tools just because of this simple self-test matter.

Alex

>
> 3. WG Chairs will control the virtual queue, unmuting and muting of
> remote participants
>
> 4. The agenda for the WG sessions, as well as more detail on how to
> use Meetecho to participate, can be found here:
> https://ietf95.conf.meetecho.com/index.php/.
>
>