Re: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remote recording - RTC-Web client acting as SIPREC session recording client]

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Thu, 08 September 2011 14:57 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 5D42621F84DA for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level:
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HD8EId9wypGd for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:57:19 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 01BB421F84D7 for <rtcweb@ietf.org>; Thu, 8 Sep 2011 07:57:18 -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 p88ExVFc009914; Thu, 8 Sep 2011 10:59:31 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 8 Sep 2011 10:58:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC6E37.C2DE6882"
Date: Thu, 8 Sep 2011 20:28:20 +0530
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510F0988@sonusinmail02.sonusnet.com>
In-Reply-To: <4E68D182.2090003@alvestrand.no>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remote recording - RTC-Web client acting as SIPREC session recording client]
Thread-Index: AcxuM95mzOqoGZSMTjeF5HNSB5K8YwAA9IvQ
References: <A444A0F8084434499206E78C106220CA0B00FDB08B@MCHP058A.global-ad.net> <89177AB2-F721-47E4-8471-2180EDA10615@voxeo.com> <A444A0F8084434499206E78C106220CA0B00FDB34D@MCHP058A.global-ad.net> <496EE152-41F2-49AB-A136-05735FE5A9F9@voxeo.com><101C6067BEC68246B0C3F6843BCCC1E31018BF6BE2@MCHP058A.global-ad.net> <4E540FE2.7020605@alcatel-lucent.com> <2E239D6FCD033C4BAF15F386A979BF5106423F@sonusinmail02.sonusnet.com> <4E6595E7.7060503@skype.net> <4E661C83.5000103@alcatel-lucent.com> <4E668FB3.9020601@skype.net> <2E239D6FCD033C4BAF15F386A979BF510F08FE@sonusinmail02.sonusnet.com> <4E67AD3D.9000005@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F090F@sonusinmail02.sonusnet.com> <4E686663.1050900@alvestrand.no> <4E68CB68.3020100@alcatel-lucent.com> <4E68D182.2090003@alvestrand.no>
From: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
To: "Harald Alvestrand" <harald@alvestrand.no>, <igor.faynberg@alcatel-lucent.com>
X-OriginalArrivalTime: 08 Sep 2011 14:58:27.0770 (UTC) FILETIME=[C40329A0:01CC6E37]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remote recording - RTC-Web client acting as SIPREC session recording client]
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, 08 Sep 2011 14:57:20 -0000

Harald,

 

I'm talking about INVITE subset only.

 

Thanks

Partha

 

From: Harald Alvestrand [mailto:harald@alvestrand.no] 
Sent: Thursday, September 08, 2011 8:00 PM
To: igor.faynberg@alcatel-lucent.com
Cc: Ravindran Parthasarathi; Matthew Kaufman; rtcweb@ietf.org
Subject: Re: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remote
recording - RTC-Web client acting as SIPREC session recording client]

 

On 09/08/11 16:04, Igor Faynberg wrote: 



On 9/8/2011 2:53 AM, Harald Alvestrand wrote: 

 

...



But sure - if you want us to implement some part of SIP, *please start
stating what part* rather than making wooly statements.


I thought I had already proposed a subset: INVITE, SUBSCRIBE/NOTIFY, and
REFER.


That's the commands. What are the parameters?

As I've said before, unless I've misunderstood what SUBSCRIBE/NOTIFY are
for (I think they are just for presence), I want them totally outside
the scope of RTCWEB; they are appropriate for implementation in
Javascript if someone needs them.

I don't know what REFER is for well enough to have an opinion of whether
it's relevant.

             Harald