[rtcweb] Possible new use case

"Elwell, John" <john.elwell@siemens-enterprise.com> Tue, 26 July 2011 20:14 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F248C11E80A7 for <rtcweb@ietfa.amsl.com>; Tue, 26 Jul 2011 13:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.79
X-Spam-Status: No, score=-103.79 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xza9iEF-NWX4 for <rtcweb@ietfa.amsl.com>; Tue, 26 Jul 2011 13:14:33 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com []) by ietfa.amsl.com (Postfix) with ESMTP id 06E4C11E8095 for <rtcweb@ietf.org>; Tue, 26 Jul 2011 13:14:33 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown []) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 1C7C523F043E for <rtcweb@ietf.org>; Tue, 26 Jul 2011 22:14:31 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([]) by MCHP063A.global-ad.net ([]) with mapi; Tue, 26 Jul 2011 22:14:31 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Tue, 26 Jul 2011 22:14:29 +0200
Thread-Topic: Possible new use case
Thread-Index: AcxL0J/zCRj4YbfDSkqYoi0HHxuLMw==
Message-ID: <A444A0F8084434499206E78C106220CA08F1D090A7@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [rtcweb] Possible new 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, 26 Jul 2011 20:14:34 -0000

(Not sure whether this should go to the W3C list,  but trying the IETF list to start with)

I raised this during the WEBRTC session on Saturday.

Does anyone have any interest in adding a use case concerning recording of real-time media at a remote recorder? I noticed something on local recording in the proposed APIs, but remote recording might have other impacts, e.g.,
- taking a stream from a capture device (mic, camera) and sending it not only to the remote browser but also to a remote recorder;
- taking a stream from the remote browser and sending it to a remote recorder (as well as rendering locally);
- possibly mixing the two streams (in case of audio) and sending as a single mixed stream to the recording device.


John Elwell
Tel: +44 1908 817801 (office and mobile)
Email: john.elwell@siemens-enterprise.com

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.