Re: IAOC requesting input on (potential) meeting cities

Fernando Gont <fgont@si6networks.com> Fri, 14 April 2017 16:32 UTC

Return-Path: <fgont@si6networks.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 47C091294C0 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 iQuJqZoQBXhD for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:32:51 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 425F9126C23 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:32:51 -0700 (PDT)
Received: from [192.168.0.228] (176-35-156-161.xdsl.murphx.net [176.35.156.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id F3B668085F; Fri, 14 Apr 2017 18:32:48 +0200 (CEST)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: dcrocker@bbiw.net, IETF <ietf@ietf.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com> <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <fd39aaf7-4674-73e4-712d-83feab48303b@si6networks.com>
Date: Fri, 14 Apr 2017 17:32:16 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UaygckfUGoB6nG4hyjJHtFVZlxk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 14 Apr 2017 16:32:53 -0000

On 04/14/2017 05:11 PM, Dave Crocker wrote:
> On 4/14/2017 9:04 AM, Fernando Gont wrote:
>> FWIW, for the developing world, remote participation has possibly always
>> been a necessity.
> 
> 
> Indeed.  I hadn't understood how extensive this had become until seeing:
> 
>    https://tools.ietf.org/html/draft-elkins-ietf-remote-hubs-00#section-3

I haven't checked the I-D. However, no matter what it says, there's
remote participation with meet echo, without hubs. For instance, I
participated (and presented) remotely in two wgs during the Chicago
IETF, without "attending" any hub.



> However, there is a significant difference between their current mode of
> integration with the 'main' venue site, versus what we will need to have
> remote sites able to have nearly seamless participation in sessions.

What I tried to note is that the situation for part of the participants
is such that remote participation is already necessary.

>From the pov of participants of North America or Europe, this *might* be
different and the current situation might be a game changer. But for us
in latin maerica, remote participation has always been a need, even if
we managed to attend one or more meetings (that's kind of like "the
exception to the rule").


> Some of this is functional, such as a single queue for everyone wanting
> to speak, no matter where they are.

Agreed.


>  Some of this is much more robust
> performance and reliability (within obvious networking limitations.)
> 
> I suspect the easiest bit will be improved usability design, since the
> Meetecho folk tend to start with reasonable design and make improvements
> quickly, as experience is gained.  But yes, from some comments over the
> last two meetings, there's probably room for that improvement.

I must say that modulo issues with the network (which were probably
local on my side), the experience was great, and I must say that the
meetecho folks provided "online" help in a very timely manner (thanks!).


There's room for improvements.. but in some cases they seem to be more
about integration of local and remote participants, than with "bugs" in
the tools themselves. e.g., as you've correctly noted, it would be great
if there was a means for managing the mic queue, such that there's a
single queue, that includes remote participants.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492