IETF Logo Mail Archive

Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)

Iñaki Baz Castillo <ibc@aliax.net> Tue, 11 October 2011 08:37 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 4778221F8CCC for <rtcweb@ietfa.amsl.com>; Tue, 11 Oct 2011 01:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level:
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.201, 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 fx0BTnJ3NdNK for <rtcweb@ietfa.amsl.com>; Tue, 11 Oct 2011 01:37:23 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 89D8721F8C8D for <rtcweb@ietf.org>; Tue, 11 Oct 2011 01:37:21 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so6558760vcb.31 for <rtcweb@ietf.org>; Tue, 11 Oct 2011 01:37:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.9.3 with SMTP id j3mr1524423vcj.6.1318322240875; Tue, 11 Oct 2011 01:37:20 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Tue, 11 Oct 2011 01:37:20 -0700 (PDT)
In-Reply-To: <CALiegf=VyViX2arp0gr0dK4WN_jv=bjwP0LUAxRf=quTxrYrUQ@mail.gmail.com>
References: <CA+9kkMBi9BzDu=WOq3RG-o5nbfnUTftDg3LRBU3DFh=Kc4W5ZQ@mail.gmail.com> <CALiegfmYgQ+yb=pDp1J2_PVa1SkxTOuaUCM02Vt6-iGabwif1g@mail.gmail.com> <CA+9kkMCUTiPO3eASjn0mbRA9YCF6TMmGGOjQ4NkVkvzVMN39Gg@mail.gmail.com> <CALiegfnx=qoS_pqyC45WVEYEFqj-3eP9g_kyhAUaOO6He_UEfw@mail.gmail.com> <CA+9kkMCibnPLrEq1234bUMXpiKBK0+22mqwYOM__CpcO2nOayg@mail.gmail.com> <CALiegfms2bt-WPtMeosFQz3-aSf2L6mfX+i68tw45sSgix561Q@mail.gmail.com> <4E8D6507.8000707@ericsson.com> <CALiegf=VyViX2arp0gr0dK4WN_jv=bjwP0LUAxRf=quTxrYrUQ@mail.gmail.com>
Date: Tue, 11 Oct 2011 10:37:20 +0200
Message-ID: <CALiegfn15szv-2yXeWptWjsQC2CwVODg_X90gD4odZkCR0LzvA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)
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 08:37:24 -0000

2011/10/7 Iñaki Baz Castillo <ibc@aliax.net>:
>> To clarify, what I see the question for the WG is how the signalling
>> model for RTCWEB session establishment is intended to work. Thus the
>> drafts intended for answering this needs to be focused on describing a
>> signalling model.
>
> Yes, agreed.
>
>
> Regards.
>
>
> PS: SIP over WebSocket just works fine. A demonstration next week.


Hi, as told in other thread, the demonstration and video of SIP over
WebSocket is already available:

  http://sip-on-the-web.aliax.net/

So this becomes a signaling protocol example for RTCweb, a *known*
signaling protocol in fact (so we can figure what we need from the
future RTCweb JS API in order to deal with SDP's and media sessions).


Regards.



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

v2.23.0 | Report a Bug | By Email