W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2016

Summary of decisions made at May 27th virtual meeting

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 2 Jun 2016 08:45:52 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B3755A988@ESESSMB209.ericsson.se>
All,

below is a summary of what was decided at the meeting (minutes at [1]).
This is posted to the list to provide the opportunity for those not at
the meeting to object if there is something they find unreasonable.

* receiver.track.stop() will not stop the transceiver, it will continue
to be alive and send RTCP (related to [2])
* We will add an API control whether or not DTX is used (so the app can
decide to not use it even if DTX/CN is negotiated in the SDP O/A).
Exactly what the API will look like is still discussed ([3]).
* We will add a table summarizing RTCRtpEncodingParameters attributes as 
proposed in [4]
* We will use both MIME type _and_ subType ([5])
* We will not make addTransceiver/addTrack async, which means transport
can in some situations be null [6]
* Adding the same track several times via supplying it as argument to
addTransceiver() will stay allowed [7]
* We will not add (back) legacy methods like addStream or removeStream
[8] or related events.

If we hear no objections within a week we will consider the above as WG
consensus.

Stefan for the chairs


[1] http://www.w3.org/2016/05/27-webrtc-minutes.html
[2] https://github.com/w3c/webrtc-pc/pull/662
[3] https://github.com/w3c/webrtc-pc/pull/675
[4] https://github.com/w3c/webrtc-pc/pull/646
[5] https://github.com/w3c/webrtc-pc/pull/648
[6] https://github.com/w3c/webrtc-pc/pull/666
[7] https://github.com/w3c/webrtc-pc/issues/583
[8] https://github.com/w3c/webrtc-pc/issues/568
Received on Thursday, 2 June 2016 08:46:26 UTC

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