Re: [vmeet] Suggestion
"HANSEN, TONY L" <tony@att.com> Fri, 08 April 2016 18:57 UTC
Return-Path: <tony@att.com>
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 1088A12D597;
Fri, 8 Apr 2016 11:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7,
RCVD_IN_MSPIKE_H2=-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 VRpYLEBqxDOD; Fri, 8 Apr 2016 11:57:54 -0700 (PDT)
Received: from mx0b-00191d01.pphosted.com (mx0b-00191d01.pphosted.com
[67.231.157.136])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 9332412D58E;
Fri, 8 Apr 2016 11:57:54 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1])
by m0049459.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id
u38Irgdk012641; Fri, 8 Apr 2016 14:57:49 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24])
by m0049459.ppops.net-00191d01. with ESMTP id 226h0sc4x6-1
(version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
Fri, 08 Apr 2016 14:57:49 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1])
by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u38IvmGl001418;
Fri, 8 Apr 2016 14:57:49 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241])
by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u38IvhB3001304
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Fri, 8 Apr 2016 14:57:46 -0400
Received: from MISOUT7MSGHUBAB.ITServices.sbc.com
(MISOUT7MSGHUBAB.itservices.sbc.com [130.9.129.146]) by mlpi409.sfdc.sbc.com
(RSA Interceptor); Fri, 8 Apr 2016 18:57:23 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by
MISOUT7MSGHUBAB.ITServices.sbc.com ([130.9.129.146]) with mapi id
14.03.0248.002; Fri, 8 Apr 2016 14:57:23 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: "team@meetecho.com" <team@meetecho.com>, "vmeet@ietf.org" <vmeet@ietf.org>,
"wgchairs@ietf.org" <wgchairs@ietf.org>
Thread-Topic: [vmeet] Suggestion
Thread-Index: AQHRkbjEqMiNZSUw7k+msfYSQ1DChZ+An8yA///NwAA=
Date: Fri, 8 Apr 2016 18:57:22 +0000
Message-ID: <510C575C-3F58-4CFC-9746-F1613D85BC32@att.com>
References: <62592448-DE03-4FAA-9974-1DF2899CA02E@cisco.com>
<640096FA-BD5A-4149-85D4-361323910EF0@isoc.org>
<5707F0FF.8050806@dcrocker.net>
In-Reply-To: <5707F0FF.8050806@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.110.240.51]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D66F372DB3D2A54D9EDD4E91E0944479@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, ,
definitions=2016-04-08_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy
score=0 spamscore=0
suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0
classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603180000
definitions=main-1604080279
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/wdTC6CfVZ3ktFcpD_kTx6Ww8Dx4>
Subject: Re: [vmeet] Suggestion
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: Fri, 08 Apr 2016 18:57:57 -0000
On 4/8/16, 1:57 PM, "vmeet on behalf of Dave Crocker" <vmeet-bounces@ietf.org on behalf of dhc@dcrocker.net> wrote: >On 4/8/2016 10:03 AM, Ray Pelletier wrote: >> I really like the idea of the chair cockpit. For example, we could get Meetecho to pre-load the slides that have been loaded in to the tools site (and all of the associated drafts), have their laptop connected to both projectors, and have their laptop be the place where you navigate the decks. The meetecho team was fantastically helpful this week, springing into action whenever you said their name in the jabber channel. That could be made more discoverable in a tweaked UI. > > >In practical terms, this needs one person focused on running the meeting >and a second person, sitting next to the first, running the meeting's >integrated tech cockpit. > >More generally: > > We should formulate basic operational scenarios for each relevant >actor (chair running the meeting, chair operating the cockpit, >presenters in the room, presenters not in the room, audience in the >room, audience not in the room. > > And we should formulate templates for how they interact. > >I think we are remarkably close to being able to make things work quite >well. Maybe not reaching the magical 'seamlessly', but quite well. > > From my experience this week, the biggest deficiency is queue >management. The virtual queue, for remote participants, worked >usefully, but have in-room folk be in a separate queue creates a >juggling problem operationally. Things will get far simpler if/when we >figure out a workable way to get in-room folk also be listed in the >virtual queue.[*] > >I suspect there is also an issue with the virtual queue, in terms of >remote hubs, if they also have in-room microphones. > >Anyhow, defining the scenarios we want to support and targeting them is >what we should do. And if we want this to be real for IETF 100, we'd >better target a serious dress rehearsal for IETF 98. > >d/ > >[*] I suspect we are also going to want two or more cameras in a room, >so that folk can see chairs, in-room speaker, and audience-at-microphone >simultaneously. Running a tech cockpit might be a task that could/should be offloaded from the chairs. When I was a chair, I found having to fiddle with all of the "tech stuff" to be distracting from actually paying attention to the meeting itself, which is where my focus as a chair needed to be. Tony
- [vmeet] Suggestion Fred Baker (fred)
- Re: [vmeet] Suggestion Joe Hildebrand (jhildebr)
- Re: [vmeet] Suggestion Ray Pelletier
- Re: [vmeet] Suggestion Dave Crocker
- Re: [vmeet] Suggestion HANSEN, TONY L
- Re: [vmeet] Suggestion Dave Crocker
- Re: [vmeet] Suggestion Michael Richardson
- Re: [vmeet] Suggestion Paul Kyzivat
- Re: [vmeet] Suggestion Lee Howard
- Re: [vmeet] Suggestion Howard, Lee
- Re: [vmeet] Suggestion Fred Baker (fred)
- Re: [vmeet] Suggestion Fred Baker (fred)
- Re: [vmeet] Suggestion Fred Baker (fred)
- Re: [vmeet] Suggestion Paul Kyzivat
- Re: [vmeet] Suggestion Michael Richardson
- Re: [vmeet] Suggestion Meetecho IETF support
- Re: [vmeet] Suggestion Dave Crocker
- Re: [vmeet] Suggestion John C Klensin
- Re: [vmeet] Suggestion bruno.decraene