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

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Thu, 08 September 2011 14:53 UTC

Return-Path: <igor.faynberg@alcatel-lucent.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 E13BD21F84B2 for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level:
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EAmdQwpyk+yK for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:53:11 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 5001F21F849D for <rtcweb@ietf.org>; Thu, 8 Sep 2011 07:53:10 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p88EsxCI028790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Sep 2011 09:54:59 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p88Esxci021711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Sep 2011 09:54:59 -0500
Received: from [135.244.18.36] (faynberg.lra.lucent.com [135.244.18.36]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p88EswxB020129; Thu, 8 Sep 2011 09:54:58 -0500 (CDT)
Message-ID: <4E68D742.4010203@alcatel-lucent.com>
Date: Thu, 08 Sep 2011 10:54:58 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
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>
In-Reply-To: <4E68D182.2090003@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
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
Reply-To: igor.faynberg@alcatel-lucent.com
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:53:12 -0000

Well,  maybe we should take it off-line--I will be happy to explain a 
few things in October. Just some in-line answers:

On 9/8/2011 10:30 AM, Harald Alvestrand wrote:
>> I thought I had already proposed a subset: INVITE, SUBSCRIBE/NOTIFY, 
>> and REFER.
> ...
>
> That's the commands. What are the parameters?

My proposal is to populate the methods with parameters in the JavaScript 
application.
>
> As I've said before, unless I've misunderstood what SUBSCRIBE/NOTIFY 
> are for (I think they are just for presence), 

No, no, no! Not just for presence, although it can be used for presence. 
  These precious methods came from PINT, how could you forget this! 
  They allow the client to subscribe for an event at the server and then 
receive notifications asynchrously.  This specific feature cannot be 
implemented using HTTP (just as INVITE cannot).  We used them in PINT 
pretty much to enable the client to learn when PSTN call is 
disconnected, but the SIP group had found many other uses later.

Again, my objective is to ensure that SIP (with all its bell and 
whistles) can be supported by a JS application.  I am just starting to 
study the code kindly sent my way a few minuts ago, but when I am 
convinced that this can be done based on WebSocket alone, I will stop 
harping on this.

Igor