Re: [rtcweb] Review request for RTCWeb standard signaling protocol

Saul Ibarra Corretge <saul@ag-projects.com> Sat, 08 October 2011 13:43 UTC

Return-Path: <saul@ag-projects.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 8688B21F8AED for <rtcweb@ietfa.amsl.com>; Sat, 8 Oct 2011 06:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611]
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 brYCIbIJgsiQ for <rtcweb@ietfa.amsl.com>; Sat, 8 Oct 2011 06:43:01 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id D98DB21F8ACC for <rtcweb@ietf.org>; Sat, 8 Oct 2011 06:43:00 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 3D859B01B7; Sat, 8 Oct 2011 15:46:15 +0200 (CEST)
Received: from [192.168.1.134] (235.4.222.87.dynamic.jazztel.es [87.222.4.235]) by mail.sipthor.net (Postfix) with ESMTPSA id 68016B0057; Sat, 8 Oct 2011 15:46:15 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Saul Ibarra Corretge <saul@ag-projects.com>
In-Reply-To: <CABRok6kd+QavT0ThBtHhygiscvs8OxtWwd2Zo_7+GcgYZW9eww@mail.gmail.com>
Date: Sat, 8 Oct 2011 15:46:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <59F098F9-4A9E-4D85-B9E7-A53D3ED1C6BE@ag-projects.com>
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com> <4E8AC222.4050308@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com> <CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com> <393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com> <CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com> <CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com> <CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com> <91986BEB-B85F-483D-A1DA-46236B2592D9@ag-projects.com> <CABRok6kd+QavT0ThBtHhygiscvs8OxtWwd2Zo_7+GcgYZW9eww@mail.gmail.com>
To: Neil Stratford <neils@belltower.co.uk>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Sat, 08 Oct 2011 13:43:01 -0000

On Oct 8, 2011, at 3:34 PM, Neil Stratford wrote:

> On Sat, Oct 8, 2011 at 10:30 AM, Saul Ibarra Corretge <saul@ag-projects.com>; wrote:
> 
> On Oct 7, 2011, at 1:53 PM, Neil Stratford wrote:
> > - No server side infrastructure (SIP proxies etc) to maintain or configure.
> >
> > - No special understanding in the server side web application beyond discovering peer identities you might want to communicate with.
> 
> Looks like some zeroconf style thing, it could be an interesting thing to explore. Do you have any ideas on how the discovery would work over the Internet?
> 
> I imagine a signalling protocol such as this would look a lot like p2psip, though there is something interesting about baking a p2p overlay network into the browser and exposing it through an API that could then be used to build all kinds of services in javascript, including p2p SIP signalling for RTC.
> 
> The great thing about *not* defining a signalling protocol is that we are free to experiment with signalling in all kinds of ways.

I'm all for it :-)

-- 
Saúl Ibarra Corretgé
AG Projects