IETF Logo Mail Archive

Re: [rtcweb] Review request for RTCWeb standard signaling protocol

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Mon, 17 October 2011 13:56 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 961D821F8677 for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 06:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Nt8Xhg6CogbN for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 06:56:59 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 07F6E21F8672 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 06:56:58 -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 p9HDvV40020643; Mon, 17 Oct 2011 09:57:31 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Oct 2011 09:56:57 -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: Mon, 17 Oct 2011 19:26:55 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF5115993F@sonusinmail02.sonusnet.com>
In-Reply-To: <8486C8728176924BAF5BDB2F7D7EEDDF3E0917F9@ucolhp4d.easf.csd.disa.mil>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Review request for RTCWeb standard signaling protocol
Thread-Index: AcyE58qiQsg22CmbRQ+ec/AyTlzr8wHt+TLwAAzwHoAAADNJ4A==
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com><4E8AC222.4050308@alvestrand.no><2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com><CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com><393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com><CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com><CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com><CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF511598EE@sonusinmail02.sonusnet.com> <8486C8728176924BAF5BDB2F7D7EEDDF3E0917F9@ucolhp4d.easf.csd.disa.mil>
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: "Roy, Radhika R USA CIV (US)" <radhika.r.roy.civ@mail.mil>, Neil Stratford <neils@belltower.co.uk>
X-OriginalArrivalTime: 17 Oct 2011 13:56:57.0476 (UTC) FILETIME=[A2893C40:01CC8CD4]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Mon, 17 Oct 2011 13:56:59 -0000

Hi Radhika,

I agree with you for "proxy" requirement and it is classified as
"federation" in RTCWeb which is outside the scope of current discussion.


IOW, single RTCWeb server knows where to route the session between any
two known RTCWeb client but RTCweb client will not aware how to route to
other RTCWeb client.

Thanks
Partha

>-----Original Message-----
>From: Roy, Radhika R USA CIV (US) [mailto:radhika.r.roy.civ@mail.mil]
>Sent: Monday, October 17, 2011 7:21 PM
>To: Ravindran Parthasarathi; Neil Stratford
>Cc: rtcweb@ietf.org
>Subject: RE: [rtcweb] Review request for RTCWeb standard signaling
>protocol
>
>Folks:
>
>If servers are intelligent enough to "route" the calls among
themselves,
>there are no need for any proxies.
>
>So, proxies are needed for "routing" in the application layer.
>
>BR/Radhika
>
>-----Original Message-----
>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
Behalf
>Of Ravindran Parthasarathi
>Sent: Monday, October 17, 2011 3:45 AM
>To: Neil Stratford
>Cc: rtcweb@ietf.org
>Subject: Re: [rtcweb] Review request for RTCWeb standard signaling
>protocol
>
><snip> My argument is that if we want the ultimate goal of simplicity
>for end user web developers then we should minimise everything they
have
>to touch - and that includes removing any requirement for server side
>infrastructure beyond the basic bare minimum, which would mean no SIP
>proxies, no websocket servers etc etc.
>
>
>
>But as I said, we don't need to standardise a protocol at all, so we
>shouldn't. If we are lucky we'll see a whole spectrum of solutions.
>
> </snip>
>
>
>
>Without server interaction, it is not possible for browser to establish
>the session with other browser. Unlike other endpoint, browser needs
>server to provide routing or  perform the authentication or atleast
>configuration information. AFAIK, RTCWeb client to RTCWeb client is not
>the motive of the work. If so, SIP is the IETF protocol between RTCWeb
>client to RTCWeb client which MUST be recommended because of the UA to
>UA communication nature. IOW, RTCWeb server signaling plays the key
role
>which calls for standardization as browser & RTCWebserver is not
>required from the same vendor.
>
>
>
>Thanks
>
>Partha
>
>

v2.23.0 | Report a Bug | By Email