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

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Thu, 15 September 2011 22:17 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 DA8A021F84B1 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 15:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level:
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 SBL+qC4Mml7n for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 15:17:06 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2F221F84AF for <rtcweb@ietf.org>; Thu, 15 Sep 2011 15:17:06 -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 p8FMJlEC009599; Thu, 15 Sep 2011 18:19:47 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Sep 2011 18:18:55 -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, 16 Sep 2011 03:48:53 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510F0C8C@sonusinmail02.sonusnet.com>
In-Reply-To: <4E721BF3.10505@alvestrand.no>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Proposed text - remote recording use case
Thread-Index: AcxzvYkgfUcWa7MUSWONOeb17M/tnQANdlrA
References: <A444A0F8084434499206E78C106220CA0B04921B16@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F09ED@sonusinmail02.sonusnet.com> <8357A942-21EA-4209-82DB-ADFCEB5F32EF@acmepacket.com> <A444A0F8084434499206E78C106220CA0BC0F38C34@MCHP058A.global-ad.net><2E239D6FCD033C4BAF15F386A979BF510F0B4E@sonusinmail02.sonusnet.com> <4E721BF3.10505@alvestrand.no>
From: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
To: "Harald Alvestrand" <harald@alvestrand.no>, <rtcweb@ietf.org>
X-OriginalArrivalTime: 15 Sep 2011 22:18:55.0153 (UTC) FILETIME=[74DA0A10:01CC73F5]
Subject: Re: [rtcweb] Proposed text - 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: Thu, 15 Sep 2011 22:17:07 -0000

Hi Harlad,

I agree with you in case it is just two socket from JS (app
environment). 

But in this usecase, The websocket towards recorder needs metadata which
is similar to SIPREC metadata
(http://tools.ietf.org/html/draft-ietf-siprec-metadata-04) and also, it
will have the impact on RTP model (RTP translator or mixer) of the
browser (http://tools.ietf.org/id/draft-eckel-siprec-rtp-rec-01.txt).
So, I'm thinking that it is inside the scope of RTCWeb. 

Thanks
Partha

>-----Original Message-----
>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf
>Of Harald Alvestrand
>Sent: Thursday, September 15, 2011 9:08 PM
>To: rtcweb@ietf.org
>Subject: Re: [rtcweb] Proposed text - remote recording use case
>
>On 09/14/11 07:57, Ravindran Parthasarathi wrote:
>> John,
>>
>> I'm fine with Hadriel proposal of "remote peer" instead "remote
>browser
>> or SRS" but not the original wordings.
>>
>> At this moment, I'm not convinced whether SIPREC SRS will interop
with
>> RTCWeb browser because the signaling protocol is an open item in
>RTCWeb.
>> The recording could be done by two websocket from browser wherein one
>> websocket towards webserver and other towards recorder. How these
>> entities interact with each other has to be discussed&  defined.
>Please
>> let me know the reason why this approach may not be followed in
>RTCWeb.
>My opinion:
>
>If this can be built in JS using the APIs and protocols defined by
>RTCWEB/WEBRTC, there is no need for anything more within these groups.
>
>If it cannot be built using these APIs and protocols, we need to
>consider whether these APIs and protocols need to be extended in order
>to cover this use case.
>
>The detailed building of the application is, in my opinion, out of
scope
>for RTCWEB.
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb