IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Wed, 05 October 2011 17:00 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 4870521F8C9D for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 10:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=0.044, 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 LPMXbUOTpr0C for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 10:00:01 -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 8E7CD21F8C9B for <rtcweb@ietf.org>; Wed, 5 Oct 2011 10:00:01 -0700 (PDT)
Received: by vws5 with SMTP id 5so1901578vws.31 for <rtcweb@ietf.org>; Wed, 05 Oct 2011 10:03:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.186.134 with SMTP id fk6mr2441469vdc.380.1317834189613; Wed, 05 Oct 2011 10:03:09 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Wed, 5 Oct 2011 10:03:09 -0700 (PDT)
In-Reply-To: <CA+9kkMCibnPLrEq1234bUMXpiKBK0+22mqwYOM__CpcO2nOayg@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>
Date: Wed, 05 Oct 2011 19:03:09 +0200
Message-ID: <CALiegfms2bt-WPtMeosFQz3-aSf2L6mfX+i68tw45sSgix561Q@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: 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: Wed, 05 Oct 2011 17:00:02 -0000

2011/10/5 Ted Hardie <ted.ietf@gmail.com>:
> Sorry, but do you intend to provide a draft?  It was hard for me to parse
> whether the statement above is a commitment or a statement that you don't
> have time.

Maybe not a draft, but a complete explanation and presentation of what
we have working (SIP over WebSocket + JavaScript code implementing a
SIP stack + SIP proxy implementing the WebSocket transport). And it
just works.

The draft is already done:

  http://tools.ietf.org/html/draft-ibc-rtcweb-sip-websocket-00

In fact it defines a concrete signaling protocol (well, not exactly as
it uses pure SIP, but on top of WebSocket). Of course it aim is to be
used with rtcweb for media sessions.

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

v2.23.0 | Report a Bug | By Email