[rtcweb] Need for Default signaling protocol for RTCWeb [was RE: draft-ibc-rtcweb-sip-vs-websocket]
"Ravindran Parthasarathi" <pravindran@sonusnet.com> Thu, 15 September 2011 23: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 4DFF821F8B51 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 16:44:16 -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 Z4wY9I4POmi4 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 16:44:15 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB1621F8B4D for <rtcweb@ietf.org>; Thu, 15 Sep 2011 16:44:09 -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 p8FNkndC001645; Thu, 15 Sep 2011 19:46:49 -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 19:38:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 16 Sep 2011 05:08:25 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510F0C92@sonusinmail02.sonusnet.com>
In-Reply-To: <4E4270DE-5CC3-4089-874A-FDFFB12156E7@phonefromhere.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Need for Default signaling protocol for RTCWeb [was RE: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket]
Thread-Index: AcxzjZj8wPl5zH0RShqnmFaCezvjkAAcYYZA
References: <CALiegfk6BhtzErXOQM8iSV7FC6isYUwOS1KPYCw_M1vEcNP6eQ@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F0B37@sonusinmail02.sonusnet.com><E44893DD4E290745BB608EB23FDDB7620AEC41@008-AM1MPN1-043.mgdnok.nokia.com><BLU152-W91B8D02E434D6209F379393050@phx.gbl><2E239D6FCD033C4BAF15F386A979BF510F0B39@sonusinmail02.sonusnet.com> <CALiegf=K+PbGz9eEgKzKjHFCc2n=26JKZQnMzmnCRhvoWz046A@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0B8A@sonusinmail02.sonusnet.com> <4E4270DE-5CC3-4089-874A-FDFFB12156E7@phonefromhere.com>
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Tim Panton <tim@phonefromhere.com>
X-OriginalArrivalTime: 15 Sep 2011 23:38:26.0622 (UTC) FILETIME=[90DE6DE0:01CC7400]
Cc: rtcweb@ietf.org
Subject: [rtcweb] Need for Default signaling protocol for RTCWeb [was RE: draft-ibc-rtcweb-sip-vs-websocket]
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 23:44:16 -0000
Hi Tim, I agree with you that it is possible to implement using plugins and it is highlighted in RTCWeb charter (http://tools.ietf.org/wg/rtcweb/charters) as "These are not interoperable, as they require non-standard extensions or plugins to work.". And also, the aim of this WG is to "There is a desire to standardize the basis for such communication so that interoperable communication can be established between any compatible browsers". Now, I don't the reason for implementing signaling in JavaScript or plugin or applet. Also, I don't know about native plugin but I guess that those plugin are installed as part of the browser installation. Please correct me if I'm wrong. Thanks Partha >-----Original Message----- >From: Tim Panton [mailto:tim@phonefromhere.com] >Sent: Thursday, September 15, 2011 3:19 PM >To: Ravindran Parthasarathi >Cc: Iñaki Baz Castillo; rtcweb@ietf.org >Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket > >It is worth pointing out that even with a signalling protocol agnostic >webRTC you >wouldn't _have_ to implement your signalling protocol in javascript. > >Browsers support other plugin languages - specifically it would be >possible to implement >a classic full UDP SIP stack as a java applet and delegate the media >handling to the webRTC layer. > >Chrome is moving towards support for native plugins, but it isn't clear >that they >would be suitable for this use. > >Tim. (speaking for himself) > > >On 14 Sep 2011, at 11:03, Ravindran Parthasarathi wrote: > >> Hi Inaki, >> >> <snip> >> >> The fact that there are other alternatives for signaling in the web >does not mean that using SIP is invalid. >> If I want to build a SIP phone in a web, why should I use libjingle >rather than SIP protocol? Why should I code a complex server behaving as >a gateway between Jingle and SIP protocols? >> >> Any protocol conversion (i.e. from Jingle to SIP) means loss of >features. Our draft proposes the contrary: no protocol conversion (just >SIP), and just transport protocol conversion (as already exists in SIP >when bridging UDP/TCP/TLS-TCP/SCTP...). >> </snip> >> >> I agree with your problem statement. I have raised the same concern in >http://www.ietf.org/mail-archive/web/rtcweb/current/msg00845.html. IMO, >your solution is a workaround and we will end-up with your solution in >case signaling protocol is not standardized as part of RTCWeb. >> >> Thanks >> Partha >> >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Igor Faynberg
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Thomas
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Bernard Aboba
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Dzonatas Sol
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Binod PG
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Patrick McManus
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Hadriel Kaplan
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Binod PG
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Avasarala, Ranjit
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Saúl Ibarra Corretgé
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Christer Holmberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Christer Holmberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Olle E. Johansson
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Tim Panton
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Tim Panton
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Randell Jesup
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Igor Faynberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dzonatas Sol
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Randell Jesup
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dzonatas Sol
- [rtcweb] Need for Default signaling protocol for … Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Saúl Ibarra Corretgé
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dan Wing