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

Harald Alvestrand <harald@alvestrand.no> Sat, 01 October 2011 07:25 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 1917921F8AEC for <rtcweb@ietfa.amsl.com>; Sat, 1 Oct 2011 00:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.232
X-Spam-Level:
X-Spam-Status: No, score=-108.232 tagged_above=-999 required=5 tests=[AWL=2.067, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 NadqM+sW60Df for <rtcweb@ietfa.amsl.com>; Sat, 1 Oct 2011 00:25:47 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 329EB21F8AEA for <rtcweb@ietf.org>; Sat, 1 Oct 2011 00:25:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6FC1C39E0AF; Sat, 1 Oct 2011 09:28:42 +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 jlmRJK+9YUgu; Sat, 1 Oct 2011 09:28:41 +0200 (CEST)
Received: from [192.168.1.16] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 32A8A39E038; Sat, 1 Oct 2011 09:28:41 +0200 (CEST)
Message-ID: <4E86C124.10706@alvestrand.no>
Date: Sat, 01 Oct 2011 09:28:36 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
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> <14235661-FD06-4209-8F18-8366AEC50004@phonefromhere.com> <CALiegf=Zi63zFBKO2ZRCtQ3DiansWTEG32=OTsoB2qSQLkqwnQ@mail.gmail.com>
In-Reply-To: <CALiegf=Zi63zFBKO2ZRCtQ3DiansWTEG32=OTsoB2qSQLkqwnQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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: Sat, 01 Oct 2011 07:25:48 -0000

On 09/30/2011 10:57 PM, Iñaki Baz Castillo wrote:
> 2011/9/30 Tim Panton<tim@phonefromhere.com>om>:
>>> 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.
> I don't know (yet) if a WebRTC client can establish different media
> sessions with different peers at the same time (it seems difficult as
> there is supposed to be a single microphone). If not, then at
> javascript level I can decide which session to enable and which one to
> pause (I hope). Also, if I make an outgoing call from the webbrowser
> and receive multiple 180/183 with different SDP, I could choose which
> one to render so I just establish the media session with one of them.
The scenarios-and-requirements document requires that this be supported.