IETF Logo Mail Archive

Re: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Fri, 28 October 2011 19:44 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 1382D21F84BD for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 12:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 zC077ZwvOexb for <rtcweb@ietfa.amsl.com>; Fri, 28 Oct 2011 12:44:03 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 803E821F84BB for <rtcweb@ietf.org>; Fri, 28 Oct 2011 12:44:03 -0700 (PDT)
Received: from sonusmail04.sonusnet.com (sonusmail04.sonusnet.com [10.128.32.98]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p9SJiZhm013351; Fri, 28 Oct 2011 15:44:35 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 28 Oct 2011 15:43:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Sat, 29 Oct 2011 01:13:12 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF51159D7C@sonusinmail02.sonusnet.com>
In-Reply-To: <CALiegfm4FXVBkeGLtAY7Fp=GQB8SxVtamPemUjgwdbSBGydn-w@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]
thread-index: AcyVqJpHzoIhjGncSSCQQlr4SraK2QAADa9A
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com><6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com><2E239D6FCD033C4BAF15F386A979BF51159C32@sonusinmail02.sonusnet.com><CALiegfnVaZjh1K+brd180Z9Ufheau3v6OJe6Ejv8P7wzw6ROQw@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF51159D7A@sonusinmail02.sonusnet.com><4EAAF413.8030501@alvestrand.no><2E239D6FCD033C4BAF15F386A979BF51159D7B@sonusinmail02.sonusnet.com> <CALiegfm4FXVBkeGLtAY7Fp=GQB8SxVtamPemUjgwdbSBGydn-w@mail.gmail.com>
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-OriginalArrivalTime: 28 Oct 2011 19:43:46.0838 (UTC) FILETIME=[E86D2360:01CC95A9]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]
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: Fri, 28 Oct 2011 19:44:04 -0000

Inaki,

ISTM, SIP specific functionality is pushed into WebRTC client unnecessary without well-defined WebRTC usecase. 

Thanks
Partha

>-----Original Message-----
>From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
>Sent: Saturday, October 29, 2011 1:04 AM
>To: Ravindran Parthasarathi
>Cc: Harald Alvestrand; rtcweb@ietf.org; Hadriel Kaplan
>Subject: Re: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-
>rtcweb-sip-interworking-requirements-00]
>
>2011/10/28 Ravindran Parthasarathi <pravindran@sonusnet.com>:
>> As I mentioned earlier, SIP (serial) forking requirement shall be met
>by gateway signaling and no extra requirement for browser.
>
>Do it in your gateway if you want, but don't try to mandate it please.
>As I also mentioned earlier, some of us are willing to handle forking
>in the WebRTC client (at JavaScript level) and that is perfectly
>possible.
>
>Regards.
>
>--
>Iñaki Baz Castillo
><ibc@aliax.net>

v2.23.0 | Report a Bug | By Email