W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: Proposal: Different specifications for different target audiences

From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 21 Jul 2013 16:39:51 -0700
Message-ID: <CABcZeBNyr989bVQUD0HUDhwaH4QL5pRFqGgp9pO8eNYGF8Wtcg@mail.gmail.com>
To: "piranna@gmail.com" <piranna@gmail.com>
Cc: Roman Shpount <roman@telurix.com>, cowwoc <cowwoc@bbs.darktech.org>, tim panton <thp@westhawk.co.uk>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Sun, Jul 21, 2013 at 4:33 PM, piranna@gmail.com <piranna@gmail.com>wrote:

> > P.S. We should really stop talking about signaling. I am pretty sure
> there
> > is a strong consensus that there is no need for direct browser-to-browser
> > signaling in webrtc. We have protocols for real time media and data, and
> > API. The signaling is implemented in JavaScript.
> >
> I agree, but we should start a discussion on another thread about how
> to develop a pure, server-less browser-to-browser signaling without
> parasiting other protocols since it's not really professional. On
> another thread it was suggested to me that it would be such a big
> issue that would require their own WG...

It's certainly not appropriate for this WG. Note that the IETF already has
had at least one effort in this space:


Received on Sunday, 21 July 2013 23:40:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:49 UTC