Re: [rtcweb] Low Level Javascript API Proposal avail on the webrtc list

Tim Panton <tim@phonefromhere.com> Fri, 30 September 2011 20:07 UTC

Return-Path: <tim@phonefromhere.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 0D05721F87FC for <rtcweb@ietfa.amsl.com>; Fri, 30 Sep 2011 13:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 s1kFiZVHIiMU for <rtcweb@ietfa.amsl.com>; Fri, 30 Sep 2011 13:07:48 -0700 (PDT)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id 282AA21F87E2 for <rtcweb@ietf.org>; Fri, 30 Sep 2011 13:07:48 -0700 (PDT)
Received: from [192.168.2.2] (unknown [212.183.140.36]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id 0405137A902; Fri, 30 Sep 2011 21:23:27 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <CALiegfk7UE2kDVdn50wjFzwFMeaUL3ga9ZeKwORzT6xw6T4VZA@mail.gmail.com>
Date: Fri, 30 Sep 2011 21:10:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <14235661-FD06-4209-8F18-8366AEC50004@phonefromhere.com>
References: <545388B3-3189-4291-BD1D-52898B888F3E@phonefromhere.com> <CAD5OKxt_3bnODVCWxrrrKVWO3R3Or1FjhMOHwgUzq3-h6dW0LA@mail.gmail.com> <9C0BD967-A31E-4ABF-AB6F-CD635E53B82C@phonefromhere.com> <CALiegfk7UE2kDVdn50wjFzwFMeaUL3ga9ZeKwORzT6xw6T4VZA@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Low Level Javascript API Proposal avail on the webrtc list
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: Fri, 30 Sep 2011 20:07:54 -0000

On 30 Sep 2011, at 20:18, Iñaki Baz Castillo wrote:

> 2011/9/28 Tim Panton <tim@phonefromhere.com>om>:
>> Forking presents some interesting challenges.
> 
> Not in case you implement pure SIP on top of JavaScript/WebSocket :)

So the question is - do you think that you _could_ implement SIP on top of JavaScript/WebSocket
and use the RTP/media api as described ? We tried to make them orthogonal, but I think Neil feels that
to support forking you may need additional features or flags to the calls described in the proposal.

Tim.