Re: [rtcweb] SIP on the Web: presentation and video

Neil Stratford <neils@belltower.co.uk> Tue, 11 October 2011 10:49 UTC

Return-Path: <neils@vipadia.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 6641321F8C83 for <rtcweb@ietfa.amsl.com>; Tue, 11 Oct 2011 03:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.826
X-Spam-Level:
X-Spam-Status: No, score=-2.826 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 tqZiYVlc5mjp for <rtcweb@ietfa.amsl.com>; Tue, 11 Oct 2011 03:49:41 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id D83FE21F8C74 for <rtcweb@ietf.org>; Tue, 11 Oct 2011 03:49:40 -0700 (PDT)
Received: by iaby26 with SMTP id y26so10425808iab.31 for <rtcweb@ietf.org>; Tue, 11 Oct 2011 03:49:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.24.96 with SMTP id u32mr10010501ibb.61.1318330180526; Tue, 11 Oct 2011 03:49:40 -0700 (PDT)
Sender: neils@vipadia.com
Received: by 10.231.200.146 with HTTP; Tue, 11 Oct 2011 03:49:40 -0700 (PDT)
In-Reply-To: <CABw3bnMESQO=SUvgQFJPxipBNV3tv9gof7JswjEJ919LyoskHw@mail.gmail.com>
References: <CABw3bnMESQO=SUvgQFJPxipBNV3tv9gof7JswjEJ919LyoskHw@mail.gmail.com>
Date: Tue, 11 Oct 2011 11:49:40 +0100
X-Google-Sender-Auth: ADhC199ONBv7hnaEwNlYEX08rxE
Message-ID: <CABRok6mRjcBuWdNiqr8zgsRRcX2T5-_6GWWKwG04FKxrM+syRg@mail.gmail.com>
From: Neil Stratford <neils@belltower.co.uk>
To: =?ISO-8859-1?Q?Jos=E9_Luis_Mill=E1n?= <jmillan@aliax.net>
Content-Type: multipart/alternative; boundary=0015177414281b60fc04af03aac3
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SIP on the Web: presentation and video
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: Tue, 11 Oct 2011 10:49:41 -0000

On Tue, Oct 11, 2011 at 7:28 AM, José Luis Millán <jmillan@aliax.net> wrote:

> Hi,
>
> Some weeks ago we made a concrete proposal for signalling between Web
> browser and server in RTCweb. Such a definition was described in
> "draft-ibc-rtcweb-sip-websocket-00".
>
> We don't advocate for a default signaling protocol in RTCweb (not at all).
> Current proposal is just an example of a working signaling for RTCweb based
> on SIP and carried over WebSocket.
>
> We have just uploaded a video demo in which there can be seen a real
> implementation of the mentioned draft.
>
> The components of the signalling architecture are a WebSocket capable
> SIP proxy and a SIP stack written in JavaScript. These are needed to
> make the browser became a real SIP node, capable to interact with real
> SIP World.
>
> We would like to emphasize that the aim of this video is nothing but
> showing an implementation of the proposed signalling.


This is a great demo of what you can do in javascript.

How would you deal with SIP credentials if you didn't want to expose them to
the user but instead use an existing authenticated web session? Would it
require a custom SIP authentication scheme to be implemented in the SIP
proxy/registrar?

Neil