IETF Logo Mail Archive

Re: [rtcweb] Let's define the purpose of WebRTC

Ravindran Parthasarathi <pravindran@sonusnet.com> Wed, 09 November 2011 10:41 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 682BF21F8C0E for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 02:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level:
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[AWL=-0.030, 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 rUOv4oLGMAUL for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 02:41:16 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id C99FB21F8B98 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 02:41:10 -0800 (PST)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pA9AffjG028658; Wed, 9 Nov 2011 05:41:41 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail06.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Nov 2011 05:41:04 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Nov 2011 16:11:13 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 9 Nov 2011 16:11:12 +0530
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: "Olle E. Johansson" <oej@edvina.net>, "Avasarala, Ranjit" <Ranjit.Avasarala@Polycom.com>
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AQHMm7/XxS9yQix74UmCewMPtvNQWZWe2WiAgABcZwCAAFnsgIAA1PQAgACv/gCAAAVogIAAGdwAgAHTzND//7JMAIAAEPMAgAESTSCAAAmSMIAALVkAgAAFPXD//9h2gIAAAg+AgAAA3YCAAAF5gIAAaZHQ
Date: Wed, 09 Nov 2011 10:41:12 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0134A265@inba-mail01.sonusnet.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <8A61D801-D14D-408B-9875-63C37D0CC166@acmepacket.com> <CABw3bnPE=OY_h5bM7GA6wgrXiOBL8P4J0kw1jLv-GSpHAbg=Cg@mail.gmail.com> <CABcZeBNqdkh8u=gwOvKfDCQA7rXdAyQkfaM1r2Sx10787btP6A@mail.gmail.com> <B10FEFF6-0ADC-4DB1-83BB-50A11C65EC35@acmepacket.com> <CABcZeBNSXtim_VqzqAd8Z-u4zWSjaYmsVZPN=7sDYkJsgtRAHA@mail.gmail.com> <4EB7E6A5.70209@alvestrand.no> <F8003BA9-BCD8-4F02-B514-8B883FF90F91@acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01349D81@inba-mail01.sonusnet.com> <845C03B2-1975-4145-8F52-8CEC9E360AF3@edvina.net> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@inba-mail01.sonusnet.com> <1D062974A4845E4D8A343C653804920206D3B7FD@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A105@inba-mail01.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804691DA2@HKGMBOXPRD22.polycom.com> <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com> <99C 883E4-2614-49A9-98D4-E38C8E5FA1F5@edvina.net> <1F2A2C70609D9E41844A2126145FC09804691E09@HKGMBOXPRD22.polycom.com> <2977E86F-BAB8-45F7-927F-DC4F39329A14@edvina.net>
In-Reply-To: <2977E86F-BAB8-45F7-927F-DC4F39329A14@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.54.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Nov 2011 10:41:13.0552 (UTC) FILETIME=[1A1CE500:01CC9ECC]
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
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: Wed, 09 Nov 2011 10:41:16 -0000

I agree that there is no need of negotiation for security mechanism.

I'll reply to "no standard signaling" protocol in another mail thread as part of comment to ROAP draft as request by Ted (Chair) to track WebRTC signaling related stuff.  

Thanks
Partha

>-----Original Message-----
>From: Olle E. Johansson [mailto:oej@edvina.net]
>Sent: Wednesday, November 09, 2011 3:20 PM
>To: Avasarala, Ranjit
>Cc: Iñaki Baz Castillo; Ravindran Parthasarathi; Muthu Arul Mozhi
>Perumal (mperumal); Cullen Jennings (fluffy); rtcweb@ietf.org
>Subject: Re: [rtcweb] Let's define the purpose of WebRTC
>
>
>9 nov 2011 kl. 10:45 skrev Avasarala, Ranjit:
>
>> Ok so any consensus s far on which signaling would be used for
>negotiating these parameters - SIP/Jingle/etc..
>>
>I would advice you kindly to go through the mail archives. The consensus
>seems to be "no default signaling" after a very long and intensive
>discussion.
>
>/O

v2.23.0 | Report a Bug | By Email