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

[webrtc-pc] setRemoteDescription error when rtcpMuxPolicy=negotiate is not implemented

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 May 2017 05:56:08 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-230928232-1495605366-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== setRemoteDescription error when rtcpMuxPolicy=negotiate is not implemented ==
in the constructor NotSupportedError is thrown on an attempt to use a negotiate in a browser which does not support it. If such a browser attempts to set a remote RTCSessionDescription should it reject with a specific error? The current error behaviour would be a RTCError from step 3 of that algorithm.

Also, the setConfiguration algorithm also has this:
> If configuration.rtcpMuxPolicy is set and its value differs from the connection's rtcpMux policy, throw an InvalidModificationError.

If the browser does not implement 'negotiate' and an attempt is made to use setConfiguration to change this wouldn't it be more consistent to return NotSupportedError too?

This would also allow streamlining the constructor steps by merging step 3 (mux policy) into step 5 (set the configuration). From an implementation perspective i'd prefer to throw the error from a single place.
Even if we want different errors that would be possible by tweaking the language above.

@taylor-b you might have an opinion already

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1235 using your GitHub account
Received on Wednesday, 24 May 2017 05:56:15 UTC

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