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

Summary of "What would you like to see in WebRTC next?"

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 21 Feb 2018 07:21:35 +0000
Message-ID: <CAJrXDUHtTFTX6g6Gx=9fKeDqvWtU9ptAE-wKs9ioB8RdJTANYA@mail.gmail.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
About a month ago, I sent an email to the list asking "What would you like
to see in WebRTC next?"  I'm glad to see there was a lot of input from many
people.  Having read through all the messages, here's my summary of the
common themes:

1. Many (most?) expressed a desire for a simple, low-level, decomposed
APIs. Specifically mentioned quite a few times were separate components for:
  - Connectivity (lower-level ICE)
  - Encode/Decode
  - Encryption
  - Transport (RTP/RTCP extensions or QUIC)

2.  A recurring use case was video conferencing, and with end-to-end
encryption.

3.  Another recurring use case was control over the network path used
(wifi/cell/both).

4.  QUIC was mentioned several times, but without any specific use cases.



I'm glad to see we're all roughly on the same page, and to learn what use
cases people are most interested in.  I think we can accomplish much of
this with a set of small, composable, low-level extensions specs with
roughly the break down expressed by the comments:

- ICE (extension spec already started, but could go lower-level)
- Encoders/Decoders (no spec yet, but I proposed an API at TPAC)
- WebCrypto (already exists)
- QUIC (extension spec already started)
- RTP/RTCP (ORTC is a good start, but could go lower-level)
Received on Wednesday, 21 February 2018 07:22:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 February 2018 07:22:11 UTC