[webrtc-pc] Need to specify what happens if the browser doesn't implement "negotiate" rtcpMuxPolicy from Taylor Brandstetter via GitHub on 2017-03-08 (public-webrtc@w3.org from March 2017)

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Wed, 08 Mar 2017 20:03:34 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-212841150-1489003413-sysbot+gh@w3.org>

taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc:

== Need to specify what happens if the browser doesn't implement "negotiate" rtcpMuxPolicy ==
JSEP states:

> Implementations MAY choose to reject attempts by the application to set the multiplexing policy to "negotiate".

So, what does this mean at the API level? A "NotSupportedError" being thrown by the RTCPeerConnection constructor?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1065 using your GitHub account

Received on Wednesday, 8 March 2017 20:03:40 UTC