Re: [webrtc-pc] Need to specify what happens if the browser doesn't implement "negotiate" rtcpMuxPolicy

The specification still includes "negotiate", even though there is a note stating that it is an "at risk" feature due to lack of implementer interest. 

Assuming that we don't remove the "negotiate" value of RTCRtcpMuxPolicy, then an exception should be thrown in the RTCPeerConnection constructor if the implementation doesn't support it.

GitHub Notification of comment by aboba
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 8 March 2017 22:58:15 UTC