Re: IAOC requesting input on (potential) meeting cities

<nalini.elkins@insidethestack.com> Fri, 14 April 2017 16:42 UTC

Return-Path: <nalini.elkins@insidethestack.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 40E7D129421 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level:
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 Gqwiks6kO_xA for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:42:24 -0700 (PDT)
Received: from nm8-vm1.bullet.mail.gq1.yahoo.com (nm8-vm1.bullet.mail.gq1.yahoo.com [98.136.218.224]) (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 782D0128B8E for <ietf@ietf.org>; Fri, 14 Apr 2017 09:42:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1492188144; bh=Ys1KtFsH6/zMz5m8AmS+Ne1DYq9BE9mho4WwEcD0yy8=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=ku153Wxo9ulYekeOdsq9a/ydEDTZ+rHqGYdtIj6cqYyOZWN5j8UpMpG+CnHwE/4K4x6+4k+4TYgnBBFu+AhtRvGnGkC2MwOacbTDD1aj3Mplx6ZntN4t7T7f6z1i50UVkfbVbZkWWoMMQ9NwigBcYX0XWEMH7/L2qoEFr341XC7g3gC6t//AGyPEdYgfL2PFcV/EzYm83VQz9MF0qoI8A1y4vEBHLWQOGt2j4FlKAspz8l82/FDpI5OMsX+RutT/Olk4UdLqaRnUnbMP/cq2IznM+3kPnfbxwP1rRNzDDvTIXelplyDCU34vWbVnufS6ZW2TR+Y9/lT3ves604TolQ==
Received: from [98.137.12.63] by nm8.bullet.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
Received: from [98.137.12.203] by tm8.bullet.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
Received: from [127.0.0.1] by omp1011.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 42264.74270.bm@omp1011.mail.gq1.yahoo.com
X-YMail-OSG: eqc9XvQVM1mrgkDhRPwV0G2cHMo_vKPzbDQlSeMSd3pqn1EOyriWcHJER_wtOou nFDeehv7AHJqd.YrXze9Hk3sAE_nrK1iBCz17V8CHS8p.XGqN0Gns52KNPg57CvP6PBLzNtj5.7y JtCDva7iAX91PVsWQMNmAtlCLp8lcBTuA6e2lFEjJauho9MAkYPaFLTVYYIaDJb6mJ0XVIZ0Zpf9 7fw5em.w51FLz2p5ysOzcEnHBlS3Obi4yfGhdQZ6LdW5BxzMymjZChV_Ie9fKT3RUr0.jSQVgkz_ YaBU3Cg8t4bwfaeaS8HH.BVmQ7TKf8AAeZOs0gbE_wRmnwFjzkxaEQKWSj2e6ZvAaJz9_r8DyI.J PZozBa5ZVh8dJjmga8ocg0EfVlEJ7wB7P9EjMc0SUNYm.RpHKSbWLi9uUaG2GYDwq.1ZNY6ubJUb w1M1VXTtC.vjDImFDAtOsWJeGcVD_ENdkx6Ju1_NaOhuET1u2I2vPRYWvjCcHjHxzHERzTA7zZPK TiITobvYN0CvdtSVWYaAMzSznIRu6aOv4d1sSeX33b08VqnuQlEU-
Received: from jws300014.mail.gq1.yahoo.com by sendmailws147.mail.gq1.yahoo.com; Fri, 14 Apr 2017 16:42:23 +0000; 1492188143.673
Date: Fri, 14 Apr 2017 16:42:23 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
Reply-To: <nalini.elkins@insidethestack.com>
To: <dcrocker@bbiw.net>, IETF <ietf@ietf.org>, Fernando Gont <fgont@si6networks.com>
Message-ID: <2078246913.570269.1492188143169@mail.yahoo.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <2078246913.570269.1492188143169.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9408 YahooMailBasic Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFTGd-bYmPbfEo7FfvqxA2gIij4>
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:42:26 -0000

Guys,

Sorry for the top post.  (Running out the door!)   

There were a number of volunteers in the Chicago IETF to help revise / recreate from scratch a remote hubs draft.   I was busy with other tasks but will get this going next week.

If anyone else would like to volunteer to help, pls let me know.     I have a feeling that we will end up doing virtual group work meetings every two weeks to get / review input.

Thanks,

Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

--------------------------------------------
On Fri, 4/14/17, Fernando Gont <fgont@si6networks.com> wrote:

 Subject: Re: IAOC requesting input on (potential) meeting cities
 To: dcrocker@bbiw.net, "IETF" <ietf@ietf.org>
 Date: Friday, April 14, 2017, 9:32 AM
 
 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