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

Identifying features that may not get implemented

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 29 Mar 2017 13:24:28 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <VI1PR0701MB2733A0BF9B90B7C9C8BAC5A4C9350@VI1PR0701MB2733.eurprd07.prod.outlook.com>
As you may know we are planning to request the transition of webrtc-pc 
to CR during April. One thing we would like to do before that is to 
identify features or parts of the spec that are at risk for not getting 
implemented (as has already been done for negotiation of RTPC mux [1], 
and is discussed for identity [2] and rtcp-transport [3]).

We would like to underline that this is not about removing features, it 
is about identifying features that are at risk for removal due to lack 
of implementation (as you know there is a requirement of two independent 
implementations). Identifying those features early could even help in 
getting them implemented, users that want those features may request 
them, or perhaps even contribute to getting them implemented.

Therefore we ask implementors to review webrtc-pc to identify features 
that there is no plan to implement (at least not in the near future), 
and let us know in the way you prefer (e.g. mail to this list, mail to 
chairs, github Issue).

We also plan to touch this subject at the April 4th virtual interim.

Stefan for the chairs

[1] http://w3c.github.io/webrtc-pc/#rtcrtcpmuxpolicy-enum
[2] https://github.com/w3c/webrtc-pc/issues/1074
[3] https://github.com/w3c/webrtc-pc/issues/1093
Received on Wednesday, 29 March 2017 13:26:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC