Change RTCConfiguration's rtcpMuxPolicy default to "require" (is "negotiate") |
||||
Issue descriptionFound as part of issue 658423 and https://codereview.chromium.org/2442763002 The WebRTC.PeerConnection.SelectedRtcpMuxPolicy and WebRTC.PeerConnection.RtcpMux histograms are relevant.
,
Nov 10 2016
Changed label to PeerConnection, since this is more a Blink issue than an ICE protocol issue.
,
Nov 11 2016
@foolip clarification - when the RTCConfiguration argument is optional, and the default for rtcpMuxPolicy is "require", that means that the implementation has to behave as if "require" was specified, right?
Otherwise, "new RTCPeerConnection()" and "new RTCPeerConnection({})" would have different behavior, and that would be strange.
So an implementation can't have a different default than the spec.
,
Nov 11 2016
Right, all of these need to do the same thing:
new RTCPeerConnection()
new RTCPeerConnection(null)
new RTCPeerConnection(undefined)
new RTCPeerConnection({})
new RTCPeerConnection({ rtcpMuxPolicy: undefined })
Right now, they all act like new RTCPeerConnection({ rtcpMuxPolicy: "negotiate" })
,
Nov 12 2016
FYI, here's a related bug for changing the default in the native library: https://bugs.chromium.org/p/webrtc/issues/detail?id=6030
,
Nov 14 2016
,
Dec 23 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by deadbeef@chromium.org
, Nov 10 2016