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

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Thu, 15 September 2011 21:59 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 A7CFF11E80A0 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 14:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level:
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 ZKZ+qlXLekom for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 14:59:04 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id D016611E8097 for <rtcweb@ietf.org>; Thu, 15 Sep 2011 14:59:03 -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 p8FM1kwN030934; Thu, 15 Sep 2011 18:01:46 -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:01:01 -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:30:59 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510F0C8A@sonusinmail02.sonusnet.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0BC110F5F0@MCHP058A.global-ad.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Proposed text - remote recording use case
Thread-Index: AQHMciK7XwUojQUk70aUevXP868dwpVMX0wwgAABGYCAAjHtsIAAbdhA
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> <A444A0F8084434499206E78C106220CA0BC110F5F0@MCHP058A.global-ad.net>
From: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Hadriel Kaplan" <HKaplan@acmepacket.com>
X-OriginalArrivalTime: 15 Sep 2011 22:01:01.0659 (UTC) FILETIME=[F4FFDAB0:01CC73F2]
Cc: rtcweb@ietf.org
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 21:59:04 -0000

John,

Could you please explain in detail about the reason for two websocket
from browser wherein one towards webserver and another towards recorder
(another webserver) is outside the scope of RTCWeb. Also, I guess that
it would have covered in one of usecase of RTCWeb document already.
AFAIK, there is no restriction on number of websockets from browser.

Thanks
Partha

>-----Original Message-----
>From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>Sent: Thursday, September 15, 2011 8:58 PM
>To: Ravindran Parthasarathi; Hadriel Kaplan
>Cc: rtcweb@ietf.org
>Subject: RE: [rtcweb] Proposed text - remote recording use case
>
>Partha,
>
>> -----Original Message-----
>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>> Sent: 14 September 2011 06:57
>> To: Elwell, John; Hadriel Kaplan
>> Cc: rtcweb@ietf.org
>> Subject: RE: [rtcweb] Proposed text - remote recording use case
>>
>> 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.
>[JRE] I am not saying it will not work, but I consider this to be
>outside scope of RTC-Web.
>
>John
>
>
>>
>> Thanks
>> Partha
>>
>>
>> >-----Original Message-----
>> >From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>> >Sent: Wednesday, September 14, 2011 11:21 AM
>> >To: Hadriel Kaplan; Ravindran Parthasarathi
>> >Cc: <rtcweb@ietf.org>
>> >Subject: RE: [rtcweb] Proposed text - remote recording use case
>> >
>> >
>> >
>> >> -----Original Message-----
>> >> From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com]
>> >> Sent: 13 September 2011 15:38
>> >> To: Ravindran Parthasarathi
>> >> Cc: Elwell, John; <rtcweb@ietf.org>
>> >> Subject: Re: [rtcweb] Proposed text - remote recording use case
>> >>
>> >> inline...
>> >>
>> >> On Sep 11, 2011, at 4:29 PM, Ravindran Parthasarathi wrote:
>> >>
>> >> > New requirements:
>> >> > Fyy1: The browser MUST be able to send in real-time to an
another
>> >> > browser/session recording server(SRS) that are being
>> >> transmitted to and
>> >> > received from remote browser.
>> >>
>> >> That doesn't make sense in English - *what* needs to be sent
>> >> in real-time?  Removing the word "media" broke the meaning.
>> >> Also, the media it needs to replicate/fork may not be to/from
>> >> another "remote browser" - it could be to/from a remote
>> >> gateway, SIP UA, whatever.  Really what you want to say is
>> >> to/from a "remote peer".
>> >> Same issues/comments go for the next requirement.
>> >[JRE] I agree the modified words don't make sense and would like to
>> >stick to the words I proposed at the start of this thread.
>> >
>> >>
>> >> >
>> >> > Ayy1: The web application MUST be able to ask the browser
>> >> to transmit in
>> >> > real-time to another browser/session recording
>> server(SRS) that are
>> >> > being transmitted to and received from remote browser.
>> >>
>> >> Same as above.
>> >>
>> >> > As I asked in the meeting (but couldn't discuss due to time
>> >> constraint),
>> >> > it is possible for browser to do the signaling directly
>> to the SRS
>> >> > without going through original webserver. The signaling towards
>> >> > recording is not required to be SIP but it shall be
>> websocket (let
>> >> > discuss separately). Here, the advantageous in this model
>> >> is that the
>> >> > recording signaling hop is reduced to 1 hop (browser to
>> SRS)  from
>> 2
>> >> > hops (browser to webserver, webserver to SRS).
>> >> >
>> >>
>> >> Actually, I don't think it is possible for the rtcweb browser
>> >> to properly do SIPREC, even if it had a SIP stack to do it
>> >> with.  The reason is the browser doesn't know the full call
>> >> metadata.  The browser doesn't know the calling/called party
>> >> info, for example.  Even the javascript itself may not know
>> >> it, depending on how the application provider does their
>> >> logic.  They could decide to have some state/logic be handled
>> >> by the web server, rather than all in the javascript.  For
>> >> example the javascript may just display a list of friends
>> >> using aliases or icons, and the web server may be the only
>> >> one who knows what the friend's AoR/URI actually is for that
alias.
>> >[JRE] Quite so. Metadata would come from the application, but
whether
>> >this is server-side or client-side is out of scope for RTC-Web. The
>> >important thing is that an application that is able to do the SIP
and
>> >Metadata part of SIPREC can ask the browser to do the media part.
>> >
>> >John
>> >
>> >
>> >>
>> >> -hadriel
>> >>
>> >>
>>