Re: [rtcweb] Possible new use case

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Thu, 28 July 2011 22:24 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 625CA5E8036 for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 15:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.882
X-Spam-Level:
X-Spam-Status: No, score=-2.882 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1o45pbA0H9oH for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 15:24:53 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 47B245E8007 for <rtcweb@ietf.org>; Thu, 28 Jul 2011 15:24:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1702; q=dns/txt; s=iport; t=1311891893; x=1313101493; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=eiYpffmamegykLIxVtVynt38t2b9Ka+BpQHZFFnRjiw=; b=AdIuJl+BUUHbx0HmuT+hwExWHDURheufaBF7bWDUuAY2iOp+MKcNp/o0 cacRbTyBNpM/gQwerl+ju46CwYiAZf/3nRvOAMYujrz85RFD9ByfLAipm xHI2GP602EJsbeSWLbI/9muwyzW1+CC6S3oX4VtHoQ7QRjU8d9fSUJJCM Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuUAAIPgMU6rRDoG/2dsb2JhbAA1AQEBAQMBAQERASEKOhcFAgEJEQQBAQsGIwEGARMYIw4IAQEFARYMG5drj0p3iQCkSZ47hWJfBIdZkDCLdA
X-IronPort-AV: E=Sophos;i="4.67,284,1309737600"; d="scan'208";a="7570384"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-7.cisco.com with ESMTP; 28 Jul 2011 22:24:52 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p6SMOqgp029616; Thu, 28 Jul 2011 22:24:52 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Jul 2011 15:24:46 -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: Thu, 28 Jul 2011 15:24:44 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C04F2FFD1@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA08F1D090A7@MCHP058A.global-ad.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Possible new use case
Thread-Index: AcxL0J/zCRj4YbfDSkqYoi0HHxuLMwBpFevg
References: <A444A0F8084434499206E78C106220CA08F1D090A7@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <rtcweb@ietf.org>
X-OriginalArrivalTime: 28 Jul 2011 22:24:46.0900 (UTC) FILETIME=[28449F40:01CC4D75]
Subject: Re: [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: Thu, 28 Jul 2011 22:24:54 -0000

Hi John,

I am interested in this use case and would be interested in seeing it
added.

Cheers,
Charles

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf Of Elwell, John
> Sent: Tuesday, July 26, 2011 4:14 PM
> To: rtcweb@ietf.org
> Subject: [rtcweb] Possible new use case
> 
> (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
> 
> 
> 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