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

Iñaki Baz Castillo <> Tue, 04 October 2011 22:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 202C821F8F2B for <>; Tue, 4 Oct 2011 15:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.633
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SpL7U6qpOXS0 for <>; Tue, 4 Oct 2011 15:29:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 80EB821F8E76 for <>; Tue, 4 Oct 2011 15:29:44 -0700 (PDT)
Received: by vws5 with SMTP id 5so1071113vws.31 for <>; Tue, 04 Oct 2011 15:32:50 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id i4mr1631136vdf.514.1317767570389; Tue, 04 Oct 2011 15:32:50 -0700 (PDT)
Received: by with HTTP; Tue, 4 Oct 2011 15:32:50 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Wed, 5 Oct 2011 00:32:50 +0200
Message-ID: <>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <>
To: Ted Hardie <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Oct 2011 22:29:45 -0000

2011/10/4 Ted Hardie <>om>:
> At today's Chairs call, Cullen, Magnus and I had a discussion of how to make
> progress on the signaling discussion.  We feel the mailing list discussion
> needs to have more concrete proposals in order to make progress, and so
> we're putting forward the following:
> 1) If you plan to put forward a draft proposing a concrete solution in this
> space, please send your name to the mailing list with that intent by October

Hi Ted, could you please explain what exactly are you looking for? a
concrete signaling mechanism within rtcweb? something native in
browsers? something carried by HTTP/WebSocket?

If so, I think that this should not be covered by rtcweb, which
instead should define a good API for dealing with SDP bodies (plain or
XML), create some kind of JavaScript object for mantaining each
session status and information (negotiated streams, codecs,
local/remote address...).

But for sure I miss something so I would like to know what exactly are
you looking for in your mail.

Thanks a lot.

Iñaki Baz Castillo