Re: [vmeet] PLAN: Formulating a workplan for vMeet
"Brian Rosen" <br@brianrosen.net> Mon, 20 April 2009 17:01 UTC
Return-Path: <br@brianrosen.net>
X-Original-To: vmeet@core3.amsl.com
Delivered-To: vmeet@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C09328C0FD for <vmeet@core3.amsl.com>; Mon, 20 Apr 2009 10:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level:
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aqqii5c1DPXO for <vmeet@core3.amsl.com>; Mon, 20 Apr 2009 10:01:49 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130]) by core3.amsl.com (Postfix) with ESMTP id CD06328C2CD for <vMeet@ietf.org>; Mon, 20 Apr 2009 10:01:49 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROS3VMxp) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1LvwqK-00032x-UB; Mon, 20 Apr 2009 11:59:41 -0500
From: Brian Rosen <br@brianrosen.net>
To: 'Doug Otis' <doug.mtview@gmail.com>
References: <49DE44DD.4060202@dcrocker.net> <200904162018.n3GKISLs012182@cichlid.raleigh.ibm.com> <49E889FC.5010108@dcrocker.net> <ADF86A1B-5F28-439B-B4DC-BC6F4B40AFB1@cs.columbia.edu> <49E8A89F.1000709@dcrocker.net> <7F75115C-5AA5-41F1-9C02-F8BE56FEF016@cs.columbia.edu> <49E8B241.2060808@dcrocker.net> <371C6BE6-4052-4709-A2FD-0E0AF08360F8@cs.columbia.edu> <C89123BF-1845-4400-910A-B5A4BF85F125@gmail.com> <07c801c9c13c$17d2a890$4777f9b0$@net> <D40925A3-BDD4-4EB2-8AA7-442A1940BE9A@gmail.com>
In-Reply-To: <D40925A3-BDD4-4EB2-8AA7-442A1940BE9A@gmail.com>
Date: Mon, 20 Apr 2009 13:02:56 -0400
Message-ID: <094e01c9c1d9$dbd652d0$9382f870$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnB179lfAn2jz1bTZyZCOEtkVmzVwAAR/8w
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: vMeet@ietf.org, dcrocker@bbiw.net
Subject: Re: [vmeet] PLAN: Formulating a workplan for vMeet
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Apr 2009 17:01:51 -0000
Someone must have solved the audio problem we're looking at, although it would not be the WebEx audio client. If not, we have work to do, but it's applied engineering and not research. It's a mix of in room, multiple mic, plus the remote participants. I've never seen it done well, but someone must have solved the problems. I'm not as enthused as you are to get chairs to run the WebEx session. I know when I'm running a meeting, it's nearly all I can do to run the slides ("Next Slide Please") as well as do real chairing. It might be different if everyone was on WebEx, but when you are chairing the live meeting, you don't look at the screen much. It's possible, but it's not great. I do think we ought to concentrate on the regular work group meeting, and not deal with the plenaries yet. That puts us within the kind of range we should easily be able to handle with the tools we are discussing. If we can get good WG meeting tools, we can extend to good plenary tools. -----Original Message----- From: Doug Otis [mailto:doug.mtview@gmail.com] Sent: Monday, April 20, 2009 12:51 PM To: Brian Rosen Cc: 'Henning Schulzrinne'; dcrocker@bbiw.net; vMeet@ietf.org Subject: Re: [vmeet] PLAN: Formulating a workplan for vMeet On Apr 19, 2009, at 3:13 PM, Brian Rosen wrote: > Uh, probably you skipped several steps. > > First of all, it's not clear that we're using WebEx's VoIP audio > system. The test doesn't, right? That mute control stuff only works > from the VoIP audio system I believe. The issue of input audio affects those presenting, or for those asking questions (perhaps via voice mail??). WebEx Event client does not support VoIP for MACs, for example. The Event client can handle up to 3000 participants, so the alternative to VoIP for a presenter would be to use a phone at $.20/minute. VoIP is limited to 500 participants, although for the Event client 3000 participants can listen. At most 7 microphones can be active, 6 + host. A teleconference can allow as many as 125 users to have speaking privileges, with 375 listening only for 500 total. > Then, the room audio, if it's fed into any bridge, is going to need > a pretty fancy echo cancellation box to deal with the room PA with > multiple mics. The basic echo cancel you get from a conference > bridge probably can't handle that. You also probably need a better > automatic gain control than you get from the bridge. WebEx provides the phone bridge, but it seems voice mail might be required to facilitate remote participant question queues. > Then we're skating around the issue of who is running the WebEX UI, > unmuting participants, .... We currently have two jobs that have a > volunteer, plus chairs usually are running slides. I'm not sure we > can round up yet another volunteer, and I'm not sure I want a chair > doing more work. The host would likely be one of the meeting chairs, which does not seem like an undue burden for them to select who is presenting. Control can be passed by presenters. The level of flexibility changes between Meeting and Events clients. It would appear that most Meetings will need to be limited to 500 participants, and that larger meetings will suffer from less compatible clients. When considering that a Net-Box attached to a digital projector and the room PA can join an entire room with the meeting, this can scale beyond the 500/3000 participant limits. WebEx offers some remote system controls, so special clients might be used by meeting chairs to enable and disable the Net-Box audio output when there is a need to enable a remote participant's ability to speak. -Doug
- Re: [vmeet] Apr 23: webex group experiment Brian Rosen
- Re: [vmeet] Apr 23: webex group experiment Doug Otis
- Re: [vmeet] Apr 23: webex group experiment Thomas Narten
- [vmeet] Apr 23: webex group experiment Dave CROCKER
- [vmeet] Oops -- Re: Apr 23^H^H24 webex group expe… Dave CROCKER
- Re: [vmeet] Oops -- Re: Apr 23^H^H24 webex group … John Buford
- Re: [vmeet] Oops -- Re: Apr 23^H^H24 webex group … Dave CROCKER
- Re: [vmeet] Oops -- Re: Apr 23^H^H24 webex group … joel jaeggli
- Re: [vmeet] Oops -- Re: Apr 23^H^H24 webex group … Eliot Lear
- Re: [vmeet] Apr 23: webex group experiment joel jaeggli
- Re: [vmeet] Apr 23: webex group experiment Melinda Shore
- Re: [vmeet] Apr 23: webex group experiment Dave CROCKER
- Re: [vmeet] Apr 23: webex group experiment Henning Schulzrinne
- Re: [vmeet] Apr 23: webex group experiment Russ Housley
- Re: [vmeet] Apr 23: webex group experiment Marc Petit-Huguenin
- Re: [vmeet] Apr 23: webex group experiment Peter Saint-Andre
- [vmeet] TOOL: Yuuguu - screen sharing and instant… Dave CROCKER
- Re: [vmeet] TOOL: Yuuguu - screen sharing and ins… Henning Schulzrinne
- [vmeet] TOOL: GoToMeeting Dave CROCKER
- [vmeet] TOOL: webex group experiment Dave CROCKER
- [vmeet] TOOL: Yugma Dave CROCKER
- [vmeet] TOOL: DimDim Dave CROCKER
- Re: [vmeet] TOOL: DimDim Peter Saint-Andre
- Re: [vmeet] TOOL: webex group experiment Marc Petit-Huguenin
- Re: [vmeet] TOOL: GoToMeeting Simon Josefsson
- [vmeet] TOOL: Adobe Connect Dave CROCKER
- [vmeet] PLAN: Formulating a workplan for vMeet Dave CROCKER
- Re: [vmeet] TOOL: DimDim joel jaeggli
- Re: [vmeet] TOOL: Adobe Connect joel jaeggli
- Re: [vmeet] TOOL: Adobe Connect Eliot Lear
- Re: [vmeet] Apr 23: webex group experiment Russ Housley
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Henning Schulzrinne
- Re: [vmeet] Apr 23: webex group experiment Olivier MJ Crepin-Leblond
- Re: [vmeet] Apr 23: webex group experiment Dave CROCKER
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Doug Otis
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Simon Josefsson
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Brian Rosen
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Doug Otis
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Brian Rosen
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Doug Otis
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Brian Rosen
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Doug Otis
- Re: [vmeet] PLAN: Formulating a workplan for vMeet Olivier MJ Crepin-Leblond
- Re: [vmeet] TOOL: Adobe Connect Thomas Narten