IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 30 September 2011 20:54 UTC

Return-Path: <ibc@aliax.net>
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 4A1B521F8AAC for <rtcweb@ietfa.amsl.com>; Fri, 30 Sep 2011 13:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.637
X-Spam-Level:
X-Spam-Status: No, score=-2.637 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 Ru-vR7+LAFHq for <rtcweb@ietfa.amsl.com>; Fri, 30 Sep 2011 13:54:19 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B63CC21F8AAA for <rtcweb@ietf.org>; Fri, 30 Sep 2011 13:54:19 -0700 (PDT)
Received: by vws5 with SMTP id 5so2389033vws.31 for <rtcweb@ietf.org>; Fri, 30 Sep 2011 13:57:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.89.177 with SMTP id bp17mr11701808vdb.447.1317416234157; Fri, 30 Sep 2011 13:57:14 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 30 Sep 2011 13:57:14 -0700 (PDT)
In-Reply-To: <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> <14235661-FD06-4209-8F18-8366AEC50004@phonefromhere.com>
Date: Fri, 30 Sep 2011 22:57:14 +0200
Message-ID: <CALiegf=Zi63zFBKO2ZRCtQ3DiansWTEG32=OTsoB2qSQLkqwnQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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:54:20 -0000

2011/9/30 Tim Panton <tim@phonefromhere.com>:
>> 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.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email