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

Jim McEachern <jim.mceachern@genband.com> Tue, 20 September 2011 01:58 UTC

Return-Path: <jim.mceachern@genband.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333C721F8AED for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 18:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYnauOzwaYp9 for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 18:58:32 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id AED8D21F84D4 for <rtcweb@ietf.org>; Mon, 19 Sep 2011 18:58:27 -0700 (PDT)
Received: from mail.genband.com ([63.149.188.88]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKTnfz0t9CAVj1qaiJ+jDuDB5SIywnILOt@postini.com; Mon, 19 Sep 2011 19:00:57 PDT
Received: from owa.genband.com ([172.16.21.98]) by mail.genband.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 19 Sep 2011 20:59:42 -0500
Received: from GBPLMAIL03.genband.com ([fe80::81ee:2d58:ca01:fb9a]) by gbex02.genband.com ([fe80::f0b6:4f10:74b0:f8b%15]) with mapi id 14.01.0289.001; Mon, 19 Sep 2011 20:59:41 -0500
From: Jim McEachern <jim.mceachern@genband.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] Call for Consensus on Use Case for Screen/Application/Desktop sharing
Thread-Index: AQHMdpoKQqo6ybJBbkGwLU8CXowJrZVUojQAgADigsQ=
Date: Tue, 20 Sep 2011 01:59:41 +0000
Message-ID: <7F213C9E-3AD9-4527-80B3-BACD280D09FA@genband.com>
References: <4E76E8E8.2050102@ericsson.com>,<4E76EF3A.4010500@alvestrand.no>
In-Reply-To: <4E76EF3A.4010500@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Sep 2011 01:59:42.0635 (UTC) FILETIME=[F69E5FB0:01CC7738]
X-TM-AS-Product-Ver: SMEX-8.0.0.4160-6.500.1024-18396.003
X-TM-AS-Result: No--31.592600-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Call for Consensus on Use Case for Screen/Application/Desktop sharing
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 01:58:33 -0000

I also support including A) in our use cases now, but deferring B) till later.

Jim 

On Sep 19, 2011, at 3:29 AM, "Harald Alvestrand" <harald@alvestrand.no> wrote:

> On 09/19/2011 09:02 AM, Magnus Westerlund wrote:
>> WG,
>> 
>> There where some discussion in the Interim meeting last week about a
>> Screen/Application/Desktop sharing support use case. My take away from
>> the discussion is that this use cases is likely well enough understood
>> to actually start a consensus call now. However, to us WG chairs it was
>> clear that the use case in question actually needs to be split into two
>> parts.
>> 
>> 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.
> I think this is a fairly well defined applicaiton (basically, take input from a synthetic source, where the synthetic source may be anything available to the browser), the baseline (but not the optimum) could simply be encoding the stuff using a default codec, and the access procedures shouldn't be much different than for microphone and camera. I support its inclusion in the document.
> 
> Note: The implementation of such a feature is far from trivial. I would not want to require that all browsers implementing RTCWeb support the feature.
>> 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.
> I see this as a  more tricky thing to get right (in most apps, the mixing of events from multiple sources depends strongly on both proper timing/sequencing and reliable delivery). I would like to not address this for now (RTCWeb version 1).
>> 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?
>> 
>> 2) Do you have additional comments for or against either of the use cases?
>> 
>> 
>> As WG chair
>> 
>> Magnus Westerlund
>> 
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> Färögatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb