W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2017

Re: My personal input to the WebRTC-NV discussions

From: westhawk <thp@westhawk.co.uk>
Date: Tue, 7 Nov 2017 09:34:07 +0000
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <9D2F51A4-73BE-4959-AD0B-8EEC400D543C@westhawk.co.uk>
To: Harald Alvestrand <harald@alvestrand.no>

> On 7 Nov 2017, at 07:24, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
> I've tried to put together my thinking about what I think we should try
> to achieve with WebRTC-NV.
> 
> Chiefly, I've tried to look for the principles: What we should keep on
> doing, what we should make it possible to live without, and what we
> should extend further.

This is good. Thanks for doing it.

I’d add one meta-point here: We need to make webRTC a first-class citizen in the
web browser, it needs to mesh with other web APIs and tools in the developers mind.

Adding promises and receivers are a big step in the right direction.

As examples, I’ve hit a couple of roadblocks in the last week:

1) WebRTC datachannel can’t be used in web or service workers - web sockets can.
2) You can’t get at the codecs. So I can’t send Opus over the datachannel or
hack my own ultralow bitrate codec in javascript and send it over srtp.

On the plus side, I’ve been doing neat things with the integration between webAudio
and webRTC, which illustrates the benefits of being a full part of the browser toolkit.

I’m looking forward to the detailed discussions.

Tim.

> 
> I've enclosed it in PDF. It looked prettier that way. Comments can also
> be made here:
> 
> https://docs.google.com/document/d/1pU4YR0hbH2IhE-s8_CggRdADps_9rambnfsOz3VH_ew/edit?usp=sharing
> 
> Harald
> 
> -- 
> Surveillance is pervasive. Go Dark.
> 
> <WebRTC NV - HTA's wishlist.pdf>
Received on Tuesday, 7 November 2017 09:34:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 November 2017 09:34:33 UTC