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

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Thu, 08 September 2011 08:45 UTC

Return-Path: <silviapfeiffer1@gmail.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 8A2C221F8B9A for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 01:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 W23Eb2QKqlEq for <rtcweb@ietfa.amsl.com>; Thu, 8 Sep 2011 01:45:06 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id D370321F8B8D for <rtcweb@ietf.org>; Thu, 8 Sep 2011 01:45:05 -0700 (PDT)
Received: by ywe9 with SMTP id 9so494104ywe.31 for <rtcweb@ietf.org>; Thu, 08 Sep 2011 01:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sKKB7f5dRX4eueic4AMTQzwuJ19layZqNFihef32Bcc=; b=B0bNIwnBv9WYS4gd7BBa5Kc2mSh427jwd85VAxa2aKevgv+wxe9cd56cPgJqxe65ks Ul0SAaDLrPEj1gV9hQEZdxMiqRLwT90m0tIV/wZjGSpNmg4j2wRpb9aKqX5tGplpU/C+ bk9CSFuyg+LSThe9MeoxSuWveLtzTKSYep7c0=
Received: by 10.236.76.225 with SMTP id b61mr2338445yhe.92.1315471616276; Thu, 08 Sep 2011 01:46:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.203.5 with HTTP; Thu, 8 Sep 2011 01:46:36 -0700 (PDT)
In-Reply-To: <3A9BCFFD-670F-49F0-9962-A00086B38FA7@edvina.net>
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> <2E239D6FCD033C4BAF15F386A979BF510F086B@sonusinmail02.sonusnet.com> <4E666926.8050705@skype.net> <43A0D702-1D1F-4B4E-B8E6-C9F1A06E3F8A@edvina.net> <033458F56EC2A64E8D2D7B759FA3E7E7020E64DC@sonusmail04.sonusnet.com> <E4EC1B17-0CC4-4F79-96DD-84E589FCC4F0@edvina.net> <4E67C3EE.50707@jesup.org> <4E67F0A2.1070308@skype.net> <CAHp8n2=Q9a14pnAojAUmdGcpuEN-QXF2DVmfckEzt4R-Ngbb8g@mail.gmail.com> <F5C58E92-F73F-4587-840C-4389C9882305@edvina.net> <CAHp8n2=sZLuwPG8Ri27oArxgfxV+iWcHTV=-x2jcQsOCbUK_hg@mail.gmail.com> <3A9BCFFD-670F-49F0-9962-A00086B38FA7@edvina.net>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 8 Sep 2011 18:46:36 +1000
Message-ID: <CAHp8n2=959=0reCCSaTm+TzbCKxihS4Hhy+CNWN6TVfPqk6ABw@mail.gmail.com>
To: "Olle E. Johansson" <oej@edvina.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remoterecording - RTC-Web client acting as SIPREC session recordingclient]
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 08:45:06 -0000

On Thu, Sep 8, 2011 at 5:13 PM, Olle E. Johansson <oej@edvina.net> wrote:
>
> 8 sep 2011 kl. 08:19 skrev Silvia Pfeiffer:
>
>> I'm arguing for leaving it out, since obviously it's already possible
>> to support it in the browser through web sockets. We wouldn't put
>> SMPTE support into browsers either just to be able to read email in
>> browsers.
>>
>> I wonder: if you are arguing for it, what is it that is not possible
>> with such a JS implementation that would require introduction of a
>> totally new technology into the browser (with all associated security
>> risks)?
> Oh, if you mean me I apologize for not being clear. I don't want SIP in rtcweb at all. Your examples are good examples on my way of thinking about rtcweb as a media layer for separate apps. That I want SIP to power those apps is a another issue :-)

Sorry. :-)
I was speaking to the larger community on this list, not you
personally when I said that. Apologies.
I think we totally agree.

Cheers,
Silvia.