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

Cullen Jennings <fluffy@cisco.com> Tue, 23 August 2011 21:55 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 E572E21F8BD8 for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 14:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.447
X-Spam-Level:
X-Spam-Status: No, score=-103.447 tagged_above=-999 required=5 tests=[AWL=-0.848, 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 GNw8W+zql6sZ for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 14:55:42 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4F60221F8BB8 for <rtcweb@ietf.org>; Tue, 23 Aug 2011 14:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1271; q=dns/txt; s=iport; t=1314136611; x=1315346211; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=om0s1OsOjJD/Th2qyTSu8Zy4JhymGbCX6735QMV8Ilw=; b=BEoh3KEPyZOR/W3gRxg7teUtupUKH5IrCbkB13H5TaC9qAUH3W5rbT+Y x9qDn+Rt/ctxvzEw0SRiwznxq48qmTouidTQubxnavBjNO4iGaRQ6In1P GNkwGez59WaY5ExejsoSfYXGn0al9UXo/vzJXy7aKs2YUgDP9wEhb8D7w M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFMhVE6rRDoG/2dsb2JhbABCp2V3gUABAQEBAgESASc2CQULC0ZXBjWHT51fAZ9AhWlfBIdhiziFDYwM
X-IronPort-AV: E=Sophos;i="4.68,271,1312156800"; d="scan'208";a="15845697"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-1.cisco.com with ESMTP; 23 Aug 2011 21:56:50 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7NLulS8029856; Tue, 23 Aug 2011 21:56:47 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: <A444A0F8084434499206E78C106220CA0B00FDAE6A@MCHP058A.global-ad.net>
Date: Tue, 23 Aug 2011 15:56:46 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AF1B737-690C-48DE-A654-12E44A9644DD@cisco.com>
References: <A444A0F8084434499206E78C106220CA0B00FDAE6A@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 local 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:55:43 -0000

On Aug 22, 2011, at 8:42 AM, Elwell, John wrote:

> 4.2.xx Local Session Recording
> In this use case, the web application user wishes to record a real-time communication locally, such that transmitted and received audio, video or other real-time media are stored in one or more files. For a given medium, the two directions of transmission can be stored in the same file (mixed) or in separate files. The web application also stores metadata that gives context to the stored media.
> 
> New requirements:
> Fxx1: The browser MUST be able to store transmitted and received media in local files.
> 
> Axx1: The web application MUST be able to ask the browser to store transmitted and received media in local files, and in the case of audio at least, ask for the two directions of transmission to be stored mixed or separately.
> 
> John

I think I want something just slightly different and that is to send media that is data in the JS and to be able to hand media as data to the JS. If the JS happens to read / write that to a file that is fine with me but this allows the JS to operate on the data or synthetically generate media and opens the doors to the possibility of writing a codec in JS or NACL.