Re: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Thu, 25 August 2011 19:15 UTC

Return-Path: <pravindran@sonusnet.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 2D83221F8AFA for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2011 12:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level:
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 JmtyLleXnXTT for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2011 12:15:15 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 3E88921F8582 for <rtcweb@ietf.org>; Thu, 25 Aug 2011 12:15:15 -0700 (PDT)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p7PJGuH3015131; Thu, 25 Aug 2011 15:16:56 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 25 Aug 2011 15:07:35 -0400
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: Fri, 26 Aug 2011 00:37:30 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF51064372@sonusinmail02.sonusnet.com>
In-Reply-To: <4E569983.8060409@mozilla.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client
Thread-Index: AcxjV+xqsjS1Al6BQ5ycPH8Bdq3ukQAAUH0Q
References: <A444A0F8084434499206E78C106220CA0B00FDB08B@MCHP058A.global-ad.net> <89177AB2-F721-47E4-8471-2180EDA10615@voxeo.com> <A444A0F8084434499206E78C106220CA0B00FDB34D@MCHP058A.global-ad.net> <496EE152-41F2-49AB-A136-05735FE5A9F9@voxeo.com> <101C6067BEC68246B0C3F6843BCCC1E31018BF6BE2@MCHP058A.global-ad.net> <4E54AB9B.9090600@jesup.org> <A444A0F8084434499206E78C106220CA0B00FDB534@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E31018BF6DF6@MCHP058A.global-ad.net> <4E554BCE.2040403@alum.mit.edu> <4E56399E.2020902@alvestrand.no> <A444A0F8084434499206E78C106220CA0B011C8D3B@MCHP058A.global-ad.net><4E5682DD.5020204@skype.net> <4E569983.8060409@mozilla.com>
From: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
To: "Timothy B. Terriberry" <tterriberry@mozilla.com>
X-OriginalArrivalTime: 25 Aug 2011 19:07:35.0029 (UTC) FILETIME=[3F7D6250:01CC635A]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client
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, 25 Aug 2011 19:15:16 -0000

Hi Timothy,

In principle, mixing is not required to be done by browser because lot
of real-time media analytical tool will be interested in un-mixed media
stream. Browser shall act as RTP translator or RTP end-point to meet the
requirement of recording and You may wish to look into Real-time
Transport Protocol (RTP) Recommendations for SIPREC draft
(https://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-rec/). 

Thanks
Partha

>-----Original Message-----
>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf
>Of Timothy B. Terriberry
>Sent: Friday, August 26, 2011 12:21 AM
>Cc: rtcweb@ietf.org
>Subject: Re: [rtcweb] Remote recording - RTC-Web client acting as
SIPREC
>session recording client
>
>Matthew Kaufman wrote:
>> But this is a bad idea. Providing APIs that let a browser send audio
>> that is being received from the other end to a third party open
>several
>> different cans of worms simultaneously. One is that there's now
>another
>
>The currently proposed MediaStream Processing API
>(http://hg.mozilla.org/users/rocallahan_mozilla.com/specs/raw-
>file/tip/StreamProcessing/StreamProcessing.html)
>essentially allows exactly this (including mixing). It doesn't make any
>distinction about whether the source of a MediaStream is a local
camera,
>a <video> tag, or a remote stream from a PeerConnection object. So if
>you want to prevent this kind of thing, you need to have an active
>method of doing so, because by default the API will allow it.
>
>> Not to mention all the protocol-level implications of being an RTP
>> mixer, if we're trying to stay true to that particular choice of
>protocols.
>
>That's a good point, and it's important to think about what the
>implications of those are, especially for a ProcessedMediaStream. This
>is not something I, personally, have thought all the way through yet.
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb