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

Re: Google's position on the WebRTC API

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 23 Jul 2013 13:00:24 +0000
To: Justin Uberti <juberti@google.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1C3339C1@ESESSMB209.ericsson.se>
On 7/23/13 5:03 AM, Justin Uberti wrote:
> With the compromise reached in the Unified Plan document,

Presumably http://www.ietf.org/id/draft-roach-mmusic-unified-plan-00.txt

> the group has
> resolved one of the biggest remaining controversies for WebRTC, and
> cleared the way for finishing up our current specs. Given the current
> implementation state, we think it's important to complete these docs
> within the next six months, reducing scope wherever possible to make
> this happen. We can then refocus on what's next.

Justin, thanks for clarifying your position.

For clarity, the documents you mention, are they the W3C docs ("Media 
Capture and Streams" + "WebRTC 1.0"), the related IETF docs, or both?


> Like other implementers, we've recognized that WebRTC has evolved
> significantly since we started - the original goal of a very simple,
> interoperable API has been joined by a desire for more direct, low-level
> control. We see this as the impetus for a different approach, operating
> a level lower than the current API. Such an API would be a fresh start
> and address the concerns currently being discussed in this group, but
> should also allow the current API to be layered on top of it.
> While the idea of starting this new work is exciting, just figuring out
> what is in and out of scope will take a considerable amount of time.
> That's why we propose scoping down and completing the current work now,
> and then tackling our new challenge.
> Justin, for the Google WebRTC team

Received on Tuesday, 23 July 2013 13:00:52 UTC

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