Re: [rtcweb] Proposed text

 

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no] 
> Sent: 13 September 2011 15:18
> To: Elwell, John
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Proposed text - remote recording use case
> 
> I like this text for capturing the use case.
> 
> I agree with Matthew that it seems to come with some special caveats 
> that we should consider whether we can solve before agreeing 
> that this 
> is an use case we MUST solve - but some of those issues may 
> be issues we 
> will face as a natural consequence of the API proposal anyway.
> 
> I suggest that Stefan add it to the use case draft under "use cases 
> considered", so that we have the text in the draft, with a 
> note that the 
> WG has not accepted this as a "must do" use case.
[JRE] Yes, in the interests of not holding things up, that would be acceptable. If we decide to promote it at some point to a "must do", we would need to add more text addressing Matthew's concerns.

John


> 
> On 09/09/11 18:41, Elwell, John wrote:
> > On yesterday's call it was agreed to work on text to cover 
> the remote recording use case. Below is text, based on an 
> earlier proposal and subsequent input. I have focused on the 
> main requirement derived from this use case, relating to 
> copying to a different peer connection, and skipped any more 
> detailed requirements concerning possible mixing of the two 
> directions of audio or injecting any tones / announcements.
> >
> > 4.2.yy Remote Session Recording
> > In this use case, the web application user wishes to record 
> a real-time communication at a remote third party (e.g., a 
> recording device), such that transmitted and received audio, 
> video or other real-time media are transmitted in real-time 
> to the third party. The third party can perform recording, 
> archiving, retrieval, playback, etc., but can also perform 
> real-time analytics on the media. A typical deployment might 
> be in a contact centre. The web application also sends 
> metadata that gives context to the stored media. The web 
> application will ensure that appropriate indications are 
> given to participants so that they are aware of recording.
> >
> > New requirements:
> > Fyy1: The browser MUST be able to send in real-time to a 
> third party 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 third party media that are 
> being transmitted to and received from remote participants.
> >
> > Comments?
> >
> > 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
> >
> 
>