Re: [vmeet] Experience as a remote attendee

Simon Pietro Romano <spromano@unina.it> Sun, 10 April 2016 21:48 UTC

Return-Path: <spromano@unina.it>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0908312D0E7 for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 14:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 Lj0xYuUjeDKr for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 14:48:42 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4152512D0F0 for <vmeet@ietf.org>; Sun, 10 Apr 2016 14:48:42 -0700 (PDT)
X-ASG-Debug-ID: 1460324919-05f27504cf6cc6500001-CNPnNC
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id P9A5aEitnzWWPBCd (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Sun, 10 Apr 2016 23:48:39 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from android-1ca95d607d90d7ed.fritz.box ([151.70.38.207]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id u3ALmb6D015379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Apr 2016 23:48:38 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <3B7CAFC7A3B7A57785E9BA26@JcK-HP8200.jck.com>
References: <D51111F6-66B9-4FAF-9B6D-FF9AE7E20D0D@att.com> <5707FBD9.6070506@gmail.com> <20160409020147.GA3997@verdi> <6EC9873F-B427-475B-B187-BE352676C4C9@isoc.org> <2FC2AFBA-5B33-44CE-A618-890B742EE5EC@unina.it> <3B7CAFC7A3B7A57785E9BA26@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----5K82SEDRD85TCNR0AOTQY9S5V34EPU"
Content-Transfer-Encoding: 8bit
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: [vmeet] Experience as a remote attendee
Date: Sun, 10 Apr 2016 23:48:37 +0200
To: John C Klensin <john@jck.com>
Message-ID: <7DDE3725-DEB8-4FF3-8C96-392C5FF36D91@unina.it>
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1460324919
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
Received-SPF: softfail (unina.it: domain of transitioning spromano@unina.it does not designate 151.70.38.207 as permitted sender)
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MISMATCH_TO, BSF_SPF_SOFTFAIL, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.28619 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header 0.00 HTML_MESSAGE BODY: HTML included in message 0.00 BSF_SPF_SOFTFAIL Custom Rule SPF Softfail
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/Vea137FM6N9efIHKCugL8bGhi70>
Cc: vmeet@ietf.org
Subject: Re: [vmeet] Experience as a remote attendee
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Apr 2016 21:48:44 -0000

Hi John,

both your thoughts are not only wise, but already on the high-priority to-do list for the Meetecho team. We'll keep you and the others updated with respect to these and other improvements to the platform.

Thanks a lot for your feedback,

Simon 

Il 10 Aprile 2016 23:38:48 CEST, John C Klensin <john@jck.com> ha scritto:
>Simon,
>
>A thought about one aspect of your note...
>
>--On Sunday, April 10, 2016 22:11 +0200 Simon Pietro Romano
><spromano@unina.it> wrote:
>
>>...
>>  In case of remote presentations, each remotee obviously adds
>> one further video stream to the pack. If you add to that the
>> lower- bandwidth Meetecho traffic (chat, client-server polling
>> and the like), plus some background traffic not generated by
>> Meetecho, you easily arrive at (or close to) saturation. 
>>...
>
>So, suppose one has several "remotees" sending video.  I don't
>think we've seen that so far with IETF, where it has tended to
>be, at most, one remote presenter at a time, but it could easily
>occur if/as we start introducing remote hubs as a serious
>participation (as distinct from outreach) mechanism.
>
>While Meetecho has relatively good arrangements (now) for
>switching the screen from a focus on slides to a focus on one or
>another of the video streams and back [1], if I'm a remote
>person who is bandwidth-limited or computer-cycles-limited, I'd
>really like to be able to control which video stream(s) are
>competing for that bandwidth.  Now, for the general case, I
>think that is unrealistic.   But it may be that a pair of
>Meetecho feeds, one more or less as present and the other
>designed to minimize bandwidth  -- fewer video panes on the
>right even you have to scan between them, maybe lower resolution
>in those panes compared to the center one, etc. -- would be
>worth thinking about.
>
>On a slightly related topic, the way Meetecho appears on my
>screen forces me to make a choice between the "Participants"
>pane and the Jabber one on the left even when there is a lot of
>spare real estate on the right (due to only one video stream
>plus monitoring my local camera which is apparently not being
>sent back to you anyway).   Possibly some rethinking of those
>relationships might be useful.
>
>best,
>   john
>
>p.s. As someone who has been doing this for most (but not all)
>meetings for a while, let me add my voice to others -- the
>meeting over meeting and year over year improvements are nothing
>short of fantastic.
>
>
>[1] Once one figures out how to use it; the "finding out how"
>parts remain a bit problematic.