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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 22 August 2011 18:42 UTC

Return-Path: <eckelcu@cisco.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 7FA2321F8B4A for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 11:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[AWL=-0.213, BAYES_00=-2.599]
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 jaD9UHfZPhLv for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 11:42:04 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 9573421F8B4C for <rtcweb@ietf.org>; Mon, 22 Aug 2011 11:42:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4212; q=dns/txt; s=iport; t=1314038590; x=1315248190; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=QH0DchbLXWjyAoS2aFshVLaUl/zQo++pGujje+0kVbw=; b=Eug2EBhE0qziqgn6AY73mN3nyDI9VjjfvGOAxKv10yUq97chV7uG5swP 9yuZMhINXI217CIbSzFhOzbYQSNTlL9+9D/yiPlZ6AMgslbOf9xx2wC0z fglmhu0MyKHV1OGV6Z9gkhI0vTrrHcZWKW+yz6CyYCdlDMbuc6do0L7Yk M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtIAAHGiUk6rRDoI/2dsb2JhbABBmDuPWneBQAEBAQEDAQEBDwEdCjQCFQQCAQgRBAEBCwYXAQYBJh8JCAEBBAESCBqHU5YvAZ5ohWlfBIdgkEmMAg
X-IronPort-AV: E=Sophos;i="4.68,264,1312156800"; d="scan'208";a="15405944"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-2.cisco.com with ESMTP; 22 Aug 2011 18:43:09 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7MIh9BH029907; Mon, 22 Aug 2011 18:43:09 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 22 Aug 2011 11:43:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Aug 2011 11:43:08 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C051BF791@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <8584590C8D7DD141AA96D01920FC6C698C880779@gbplmail03.genband.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Proposed text for remote recording use case
Thread-Index: Acxg2bMH4OnwgCTEThmECGCUEO8SogAHBiMwAAE5lPA=
References: <A444A0F8084434499206E78C106220CA0B00FDAE6B@MCHP058A.global-ad.net> <8584590C8D7DD141AA96D01920FC6C698C880779@gbplmail03.genband.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Jim McEachern" <jim.mceachern@genband.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <rtcweb@ietf.org>, <public-webrtc@w3.org>
X-OriginalArrivalTime: 22 Aug 2011 18:43:09.0224 (UTC) FILETIME=[56900A80:01CC60FB]
Subject: Re: [rtcweb] Proposed text for remote recording use case
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: Mon, 22 Aug 2011 18:42:05 -0000

Hi Jim,

SIPREC includes the notion of recording awareness, and in the case of a
recording aware device you can signal in SDP the fact that something is
being recorded rather than requiring an indication to be inserted into
the media stream. I think RTCWEB should be able to leverage this
mechanism. In that case, the indication of the media being recorded may
be communicated by the web application or the browser, but it need not
necessarily be inserted in the actual media.

Cheers,
Charles 

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf Of Jim McEachern
> Sent: Monday, August 22, 2011 11:30 AM
> To: Elwell, John; rtcweb@ietf.org; public-webrtc@w3.org
> Subject: Re: [rtcweb] Proposed text for remote recording use case
> 
> John,
> It has previously been pointed out that in some jurisdictions there is
a legal requirement to insert a
> tone (e.g. an intermittent beep) that indicates the conversation is
being recorded.  It seems like
> this would be a good thing to mention here.
> 
> If this makes sense, I'm thinking something like the following
sentence added to the end of 4.2.yy:
> "... If required, the web application will direct the browser to
insert an appropriate indication
> (e.g. an intermediate beep) into the media stream to show that the
communication is being recorded."
> 
> This also suggests an additional requirement.
> "Ayy2: The web application MUST be able to ask the browser to insert
an appropriate indication into
> the media stream to indicate that the communication is being
recorded."
> 
> I believe that F15 already covers the requirments for the browser in
this case.
> F15:         The browser MUST be able to process and mix
>                    sound objects (media that is retrieved from another
>                    source than the established media stream(s) with
the
>                    peer(s) with audio streams).
> 
> Thoughts?
> Jim
> 
> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf Of Elwell, John
> Sent: Monday, August 22, 2011 10:42 AM
> To: rtcweb@ietf.org; public-webrtc@w3.org
> Subject: [rtcweb] Proposed text for remote recording use case
> 
> 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
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb