Re: [vmeet] PLAN: Formulating a workplan for vMeet

Doug Otis <doug.mtview@gmail.com> Mon, 20 April 2009 19:50 UTC

Return-Path: <doug.mtview@gmail.com>
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 6E9893A6FFB for <vmeet@core3.amsl.com>; Mon, 20 Apr 2009 12:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 UF8wPo5mV2EM for <vmeet@core3.amsl.com>; Mon, 20 Apr 2009 12:50:12 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by core3.amsl.com (Postfix) with ESMTP id 65E1B28C0FD for <vMeet@ietf.org>; Mon, 20 Apr 2009 12:49:12 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g37so794840rvb.49 for <vMeet@ietf.org>; Mon, 20 Apr 2009 12:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=tNHYUYVRCIIxAhDzlz3Jb+W7nVLJFxxZQoxSgiS7i1U=; b=aSFQFw+ITU2JMRuyHSf2qtb3ZfyahfLfxhYxrYxmcm9xkAFkTFqjBQ9pxNzgDAu6Kf 0QM9qfjekdMm0+VHPpNHGbpYs4Ae6wZ8XWENJra7YKy8J5e5C21AAaW97rTkxH0pif/W Bnjv/JcrHfDAH92SlY9oAahKe32RBuCtZlaiM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=jlO0ebri41QbaQFMyBD5pOzPkXuNMXLGg1P/OWdPMNvkJIb5OuVt8xbUJ+G6oWZGi/ 49oRwiFjN4nA6KQMrGb4VGIYn230rQAO4EtnM62vaIw/iR2yWbk9OEQkjNH9aYvt8jn9 s/xRiCpYzCQVmuFX8mZO6+T0CqJPWwpH89cb8=
Received: by 10.114.80.18 with SMTP id d18mr1947882wab.147.1240257024939; Mon, 20 Apr 2009 12:50:24 -0700 (PDT)
Received: from SJC-Office-NAT-219.mail-abuse.org (SJC-Office-NAT-219.mail-abuse.org [168.61.10.219]) by mx.google.com with ESMTPS id k35sm7942445waf.19.2009.04.20.12.50.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 20 Apr 2009 12:50:23 -0700 (PDT)
Message-Id: <076C05E4-E094-49ED-A55A-A56351FAAE93@gmail.com>
From: Doug Otis <doug.mtview@gmail.com>
To: Brian Rosen <br@brianrosen.net>
In-Reply-To: <094e01c9c1d9$dbd652d0$9382f870$@net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 20 Apr 2009 12:50:21 -0700
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> <094e01c9c1d9$dbd652d0$9382f870$@net>
X-Mailer: Apple Mail (2.930.3)
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 19:50:13 -0000

On Apr 20, 2009, at 10:02 AM, Brian Rosen wrote:

> Someone must have solved the audio problem we're looking at,  
> although it would not be the WebEx audio client.

Agreed.  The Meeting client is limited to 500 participants and does  
not support audio broadcasts.  However, the IETF already broadcasts  
the PA audio.

>  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.

Don't think this will be much of an issue.  Need to work on developing  
utilities to allow remote participants to be heard within the room  
using a dedicated client.

> 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.

With WebEx, the presenters control their own sides and pass control.   
IMHO, WebEx should be continuously projected by a Net-Box attached to  
the projector.  There are standard brackets for attaching the Net-Box.

> I do think we ought to concentrate on the regular work group  
> meeting, and not deal with the plenaries yet.

A hybrid approach could handle both environments fairly well.    
Unfortunately, the Event client is somewhat OS limited at this time. :^(

>  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.

Agreed.

-Doug