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

[Henning Schulzrinne <[e-mail]>]

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)

- 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")

Henning

On Apr 17, 2009, at 12:45 PM, Dave CROCKER wrote:

>
>
> Henning Schulzrinne wrote:
>> I think it would be useful to have a set of requirements spelled  
>> out, both MUST and NICE TO HAVE (a new 2119 category).
>
> +1
>
> (I suppose that 'MAY' serves the nice-to-have function, in a  
> requirements spec.)
>
>
> Fred circulated an initial list of usage modes, from which one can  
> start to formulate the functional requirements:
>
>   <http://www.ietf.org/mail-archive/web/vmeet/current/msg00009.html>
>
>
> From a discussion with Fred and Eliot, I suggest the following  
> elaboration:
>
>
>
> Goals
> -----
>
> Mode Goal = MG
>
> MG-A:  Slight improvement in quality of the experience for existing  
> remote
>       participants (current model 'bis')
>
> MC-B:  Remote participants as regular, full participants in a  
> meeting (.0
>       upgrade to model; for all sessions)
>
> [MG-x:   Design team collaboration ? ]
>
> MG-C:  Individual virtual session, small scale (30?)
>
> MG-D:  Individual virtual session, large scale (200?)
>
> MG-E:  Suite of simultaneous virtual sessions
>
> MG-F:  Full IETF meeting sequence
>
>
>
> Milestones
> ----------
>
> Document the (required) IETF features for a session
>
> Specify expected/desired functional details for each MG / Revisit  
> periodically
>   (but don’t call these ‘requirements’)
>
> Slight improvement in quality of the experience for existing remote  
> participants
>   (current model 'bis')
>
> Remote participants as regular, full participants in a meeting (.0  
> upgrade to
>   model; for all sessions)
>
> [Design team collaboration ? ]
>
> Individual virtual session, small scale (30?)
>
> Individual virtual session, large scale (200?)
>
> Suite of simultaneous virtual sessions
>
> Full IETF meeting sequence
>
> d/
> -- 
>
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>