W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2011

RE: [rtcweb] Proposed text for remote recording use case

From: Elwell, John <john.elwell@siemens-enterprise.com>
Date: Wed, 24 Aug 2011 10:40:14 +0200
To: Cullen Jennings <fluffy@cisco.com>
CC: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <A444A0F8084434499206E78C106220CA0B00FDB542@MCHP058A.global-ad.net>

Since I posted the proposed text, I have attempted to clarify things in a different thread:
This may help to clarify things. My proposed text might require refinement, depending on the outcome of that other thread.

HTTP post is not what is really needed here - in common with the SIPREC work, the idea is to send real-time media in real-time (over RTP), for similar reasons that RTC-Web uses peer-to-peer RTP. Some recording devices use real-time analytics, and need to receive the information without significant delay.


> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy@cisco.com] 
> Sent: 23 August 2011 22:49
> To: Elwell, John
> Cc: rtcweb@ietf.org; public-webrtc@w3.org
> Subject: Re: [rtcweb] Proposed text for remote recording use case
> Just to try and help clarify requirements ... I suspect the 
> current requirements you wrote could be meant mostly by just 
> taking a copy of the data to and from the 
> speaker/mic/camera/screen and just sending them via a HTTP 
> post to some web service that recorded them. I suspect you 
> want something different than that so we might need to poke 
> at these requirements a bit to see what it is. Alternatively, 
> if data can be copied from one stream to anther stream using 
> the JS, does that provide everything you need or is it 
> something more. 
> (BTW... I am probably not in favor of supporting these 
> requirements in the client as it is typically not a great 
> place to do recording but that's a separate issues. Just 
> trying to clarify what we talking about)
> On Aug 22, 2011, at 8:42 AM, Elwell, John wrote:
> > 4.2.yy Remote Session Recording
> > In this use case, the web application user wishes to record 
> a real-time communication at a remote recording device, such 
> that transmitted and received audio, video or other real-time 
> media are transmitted in real-time to the remote device. The 
> remote device can perform archiving, retrieval, playback, 
> etc., but can also perform real-time analytics on the media. 
> A typical deployment might be in a contact centre. For a 
> given medium, the two directions of transmission can be 
> transmitted together (mixed) or separately. The web 
> application also sends metadata that gives context to the 
> stored media.
> > 
> > New requirements:
> > Fyy1: The browser MUST be able to send in real-time to a 
> remote recording device media that are being transmitted to 
> and received from remote participants.
> > 
> > Ayy1: The web application MUST be able to ask the browser 
> to transmit in real-time to a remote recording device media 
> that are being transmitted to and received from remote 
> participants and, in the case of audio at least, ask for the 
> two directions of transmission to be transmitted to the 
> remote recording device mixed or separately.
> > 
> > John
> > 
> > 
> > John Elwell
> > Tel: +44 1908 817801 (office and mobile)
> > Email: john.elwell@siemens-enterprise.com
> > http://www.siemens-enterprise.com/uk/
> > 
> > Siemens Enterprise Communications Limited.
> > Registered office: Brickhill Street, Willen Lake, Milton 
> Keynes, MK15 0DJ.
> > Registered No: 5903714, England.
> > 
> > Siemens Enterprise Communications Limited is a Trademark 
> Licensee of Siemens AG.
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
Received on Wednesday, 24 August 2011 08:40:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:25 UTC