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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 22 August 2011 22:55 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 06D4221F8B31 for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 15:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.808
X-Spam-Level:
X-Spam-Status: No, score=-2.808 tagged_above=-999 required=5 tests=[AWL=-0.209, 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 L5odhNijZZr4 for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 15:55:33 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 0044A21F8B2C for <rtcweb@ietf.org>; Mon, 22 Aug 2011 15:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=5302; q=dns/txt; s=iport; t=1314053799; x=1315263399; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=RLKo3P/8CF38Mkg1q8kFgG11x/Nrg/FxvH+XZkEzPPA=; b=TT2T4T1lTrSIXNcPUYXa8mhzjgjiwMfb1sCEgT9zrKMer0kKFGLF1VDQ EmU5Gz4dfQ03tg/rfCXySwZOPN6xJQyP/QlZuXQb/VVU4OGf+KbuAbtrG 46lVBMVZTsk6RdzvYTCE8iyB2W5KbxykqEirFALkkZ3sV69sMb2z1rl/7 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtIAADDeUk6rRDoI/2dsb2JhbABBmESPWneBQAEBAQEDAQEBDwEdCjQCFQQCAQgRBAEBCwYXAQYBJh8JCAEBBAESCBqHU5ZCAZ8WhWlfBIdgkEmMAg
X-IronPort-AV: E=Sophos;i="4.68,266,1312156800"; d="scan'208";a="15477686"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-8.cisco.com with ESMTP; 22 Aug 2011 22:56:38 +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 p7MMucgd009336; Mon, 22 Aug 2011 22:56:38 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 15:56:38 -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 15:56:25 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C051BF8CF@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <8584590C8D7DD141AA96D01920FC6C698C8807DC@gbplmail03.genband.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Proposed text for remote recording use case
Thread-Index: Acxg2bMH4OnwgCTEThmECGCUEO8SogAHBiMwAAE5lPAAAIaPIAAIdVww
References: <A444A0F8084434499206E78C106220CA0B00FDAE6B@MCHP058A.global-ad.net> <8584590C8D7DD141AA96D01920FC6C698C880779@gbplmail03.genband.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C051BF791@xmb-sjc-234.amer.cisco.com> <8584590C8D7DD141AA96D01920FC6C698C8807DC@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 22:56:38.0167 (UTC) FILETIME=[BFCC9270:01CC611E]
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 22:55:34 -0000

Hi Jim,

I met to recommend the latter.

Cheers,
Charles

> -----Original Message-----
> From: Jim McEachern [mailto:jim.mceachern@genband.com]
> Sent: Monday, August 22, 2011 12:02 PM
> To: Charles Eckel (eckelcu); Elwell, John; rtcweb@ietf.org;
public-webrtc@w3.org
> Subject: RE: [rtcweb] Proposed text for remote recording use case
> 
> Charles,
> Does this mean that there isn't a need to say anything, or that we
should state there is a requirement
> to  indicate the communication is being recorded, but not assume you
will have to insert something
> into the media path?
> 
> Jim
> 
> 
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Monday, August 22, 2011 2:43 PM
> To: Jim McEachern; Elwell, John; rtcweb@ietf.org; public-webrtc@w3.org
> Subject: RE: [rtcweb] Proposed text for remote recording use case
> 
> 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