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

Cullen Jennings <fluffy@cisco.com> Tue, 23 August 2011 21:47 UTC

Return-Path: <fluffy@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 A107821F8CCC for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 14:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.458
X-Spam-Level:
X-Spam-Status: No, score=-103.458 tagged_above=-999 required=5 tests=[AWL=-0.859, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kbm3TUHjD5tC for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 14:47:43 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id B403B21F8CCA for <rtcweb@ietf.org>; Tue, 23 Aug 2011 14:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=2620; q=dns/txt; s=iport; t=1314136132; x=1315345732; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=tfYfJ55DB1FAbunchHPEPNXmk+rOEh1Y9fgVSFf1Iv8=; b=C4cDirZHPAr9Fq/eWlCFd/OsryPS8OXyywF1RlLJqDZLfzWeZpl320fz Ow7Oq6cNZVPMpNbimLyj7T/vzuAh7/Zgsv+MElu9SuVEPNZvfQhQ48oM8 zvAQ3v+dqBxSjEf/0I3o7M2RoeclnH62s/ZnQu5mi+yCEvSK90/F0vsUM Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADsfVE6rRDoJ/2dsb2JhbABCp2V3gUABAQEBAgEBAQEPASc0AgkFCwtGJzAGEyKHTwSdWQGfQoVpXwSHYYs4hQ2MDA
X-IronPort-AV: E=Sophos;i="4.68,271,1312156800"; d="scan'208";a="15842489"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-6.cisco.com with ESMTP; 23 Aug 2011 21:48:52 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7NLmob9024820; Tue, 23 Aug 2011 21:48:51 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0B00FDAE6B@MCHP058A.global-ad.net>
Date: Tue, 23 Aug 2011 15:48:50 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B4385D8-C7C9-4BF3-8819-39ECE3434C31@cisco.com>
References: <A444A0F8084434499206E78C106220CA0B00FDAE6B@MCHP058A.global-ad.net>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
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: Tue, 23 Aug 2011 21:47:44 -0000

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