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

Doug Otis <doug.mtview@gmail.com> Fri, 17 April 2009 22:36 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 81CC028C148 for <vmeet@core3.amsl.com>; Fri, 17 Apr 2009 15:36:36 -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=[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 EKuYLk1x772D for <vmeet@core3.amsl.com>; Fri, 17 Apr 2009 15:36:35 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by core3.amsl.com (Postfix) with ESMTP id 8BEBD28C1AB for <vMeet@ietf.org>; Fri, 17 Apr 2009 15:36:27 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so471478rvf.5 for <vMeet@ietf.org>; Fri, 17 Apr 2009 15:37:41 -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=H8kHruWQf4As/9a2VjpUcrJMpPVvhvLFKT1yDpFkPQ0=; b=gQwekKATVEE+OpbYOcSROsKv/gVIiSnC/Cl5xAMqW+ZHWphT6IrwniSGHb8BNQ8JBt oXbx4bfUEsB8rEd7O8zjy1TqWL8l4A2qL4DQ874kMqds/OzuMr6en7+ixrY+S42duj/b zH1iJ4lvbSNmrNMGQuYIbLUI5nJmxvE3KVn7g=
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=VxxhGepv0y+DS2Lndc4PONUCZZxV5Dsr25O8G7Oeu2qsY7X3dKFR+Yhog3bi+bQEyc Afr2j0+Sl/lW0gPO86bzs592r6s1cv3xRjKm35hXVKtmOXMfqlQHFdCDw1Tk2SaXts7q OzSBb/T28taHZbwwyDt/dAcjueSfK+7ZJtFP4=
Received: by 10.140.200.14 with SMTP id x14mr1368851rvf.55.1240007861457; Fri, 17 Apr 2009 15:37:41 -0700 (PDT)
Received: from ?10.2.18.195? ([66.35.254.64]) by mx.google.com with ESMTPS id b8sm7707276rvf.2.2009.04.17.15.37.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 17 Apr 2009 15:37:40 -0700 (PDT)
Message-Id: <C89123BF-1845-4400-910A-B5A4BF85F125@gmail.com>
From: Doug Otis <doug.mtview@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <371C6BE6-4052-4709-A2FD-0E0AF08360F8@cs.columbia.edu>
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: Fri, 17 Apr 2009 15:37:37 -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>
X-Mailer: Apple Mail (2.930.3)
Cc: dcrocker@bbiw.net, vMeet@ietf.org
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: Fri, 17 Apr 2009 22:36:36 -0000

On Apr 17, 2009, at 11:42 AM, Henning Schulzrinne wrote:

> There's probably a common set of minimal requirements:
>
> - Clients (remote participants) can be Windows 2000/XP/Vista, MacOS,  
> Linux.
>
> - Presenting systems can be some subset thereof (may not need Win2K,  
> for example).
>
> - Ability to render PowerPoint and PDF MUST, OpenOffice SHOULD.
>
> - For audio, allow VoIP and PSTN dial-in (800# is MAY).
>
> - Ability to mute remote participants (e.g., to deal with someone's  
> music-on-hold system)

WebEx breaks this down to Host, Presenters, and Attendees.

Attendees are muted by default, and Presenters control the display  
once control is passed to them by the Host or other Presenters.

People located within the meeting room will not use of the Remote  
Meeting application as a means to listen.  This would create an  
extreme annoyance when local participants are speaking due to even  
slight audio delays.  Those in the room will likely listen to the  
output of the room's PA system which does not have noticeable delay.   
The audio from the PA system can be input into a Net-Box system deemed  
as an unmuted Presenter for remote participants to hear the audio.   
When it comes time to listen to external participants, they will need  
to be informed (perhaps by seeing they are not muted) AND at the same  
time, having the output of the Net-Box enabled as a feed into the PA  
system.  Enabling the output of the Net-Box only when a remote  
participant is talking will allow the room to hear remote participants  
comments or questions.

> - Audio recording
>
> Nice-to-have:
>
> - Audio MAY: speaker indication (who is talking)
>
> - Pass ability to "drive" slides to any participant.
>
> - Annotate slides in real time (highlighter, overlay text).
>
> - Text chat (already have Jabber chat rooms)
>
> - Hand raising to claim microphone spot ("floor control")

Polling system to allow participation in Hums.

Slide presentation Control.

Tokens indicating who has control.

-Doug