Re: [rtcweb] Proposed text - remote recording use case

["Ravindran Parthasarathi" <[e-mail]>]

John,

Please let me know whether the updated text works for you:

New requirements:
Fyy1: The browser MUST be able to send in real-time to an another
browser/session recording server(SRS) that are being transmitted to and
received from remote browser.

Ayy1: The web application MUST be able to ask the browser to transmit in
real-time to another browser/session recording server(SRS) that are
being transmitted to and received from remote browser.

Basically I changed "a third party media" to "an another browser/session
recording server (SRS)" because SRS is not required to be third party.
Also, there is a discussion wherein the actual participant is not known
to the browser, so I prefer "browser" rather than "participants".

As I asked in the meeting (but couldn't discuss due to time constraint),
it is possible for browser to do the signaling directly to the SRS
without going through original webserver. The signaling towards
recording is not required to be SIP but it shall be websocket (let
discuss separately). Here, the advantageous in this model is that the
recording signaling hop is reduced to 1 hop (browser to SRS)  from 2
hops (browser to webserver, webserver to SRS).

Thanks
Partha

>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On
Behalf
>Of Elwell, John
>Sent: Friday, September 09, 2011 10:12 PM
>To: [e-mail]
>Subject: [rtcweb] Proposed text - remote recording use case
>
>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: [phone] (office and mobile)
>Email: [e-mail]
>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
>[e-mail]
>https://www.ietf.org/mailman/listinfo/rtcweb