Re: [rtcweb] Call for Consensus on Use Case for Screen/Application/Desktop sharing

[Randell Jesup <[e-mail]>]

On 9/19/2011 3:02 AM, Magnus Westerlund wrote:
>
> A) Where the RTCWEB enabled browser can use a local application window,
> the whole desktop or a Screen as a media source that can be encoded and
> transported over the peerConnection for displaying/playback at the peer.
>
> B) Where a remote peer can provide one or more input types such as mouse
> and keyboard to control the local system, not only including the
> browser, but also other operating system resources. This clearly can
> only happen after additional consent, most likely on a per occasion
> consent.
>
> My interpretation is that A only allows for application sharing in
> conferencing contexts, like in the WEBEX session the Interim meeting was
> held with where we shared slides. Where the combination of A and B is
> providing for VNC/Remote desktop.
>
> Thus the question to the WG is the following.
>
> 1) Do you support or object the inclusion of use case A, B or Both in
> our Use case document?

Both.

>
> 2) Do you have additional comments for or against either of the use cases?
>
IMHO: Both use-cases involve extra-fun security issues, but both are actually
pretty compelling and useful cases to users.  Everyone I mentioned them to
at the Mozilla All-Hands event "got" the wish for these use-cases pretty
immediately.

VNC-like transfer of screen data is a particularly tough one for the current
permission and access model to enable, but that may change.  A lot of this is
likely to be tied-to or echo the security model and concerns for HTML5 "installed
webapps".


-- 
Randell Jesup
[e-mail]