W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2018

Re: What would you like to see in WebRTC next? A low-level API?

From: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>
Date: Wed, 24 Jan 2018 11:48:46 +0000
To: Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <A1AE13AD-9338-43F3-9398-5FC0823B673A@ericsson.com>

On 2018-01-23, 23:58, "Peter Thatcher" <pthatcher@google.com<mailto:pthatcher@google.com>> wrote:

Please write back to this thread and let the WG know what you'd like to see in WebRTC next and why.

Assuming the charter will cover API evolution 2-4 years ahead and not just polish the current API, my shortlist of improvements and extensions are:


  *   Extensibility using low level APIs for “ICE++”.
  *   Decrease/avoid SDP “noise” in API (and if possible contain in community discussions”.
  *   Evolution to QUIC (not taking a position on how but low level API’s interesting).
  *   Support for Machine Intelligence in Web Apps- both actuation and training of models for “smart web apps” are interesting- for instance
accessing streams in service worker for NLP/Object recognition, etc. Much can be done but I expect polishing and also security to become even more relevant than.

The last bullet raises the question of what view and role this WG takes on and in other browser API’s support for WebRTC applications. An alignment and coordination with other API’s for the benefit of ‘smart web app/site’ developers is desirable even if a large portion of work will be done in other WG’s or even WHATWG.

So I guess I am saying we should indeed leverage learnings from ‘hand-on’ experience from ORTC and WebRTC1.0 but also consider other developments in the web platform and on the Web.

My 5 cents.
Göran AP

Received on Wednesday, 24 January 2018 11:49:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 24 January 2018 11:49:13 UTC