IETF Logo Mail Archive

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

Harald Alvestrand <harald@alvestrand.no> Thu, 08 September 2011 14:28 UTC

Return-Path: <harald@alvestrand.no>
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 7E57A21F8BDE for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.003
X-Spam-Level:
X-Spam-Status: No, score=-108.003 tagged_above=-999 required=5 tests=[AWL=2.595, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 AzURH8AVzteD for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 07:28:36 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id A7B2D21F8B9F for <rtcweb@ietf.org>; Thu, 8 Sep 2011 07:28:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 91E5239E0F3; Thu, 8 Sep 2011 16:30:27 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AASqlNREWZVH; Thu, 8 Sep 2011 16:30:26 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id B87B439E074; Thu, 8 Sep 2011 16:30:26 +0200 (CEST)
Message-ID: <4E68D182.2090003@alvestrand.no>
Date: Thu, 08 Sep 2011 16:30:26 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: igor.faynberg@alcatel-lucent.com
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>
In-Reply-To: <4E68CB68.3020100@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------000600020103020508060507"
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:28:36 -0000

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

v2.23.0 | Report a Bug | By Email