New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 5 users
Status: Verified
Owner:
Closed: Dec 2016
Cc:
Components:
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment
Change default RTCP mux policy to "require"
Project Member Reported by deadbeef@webrtc.org, Jun 22 2016 Back to list
In section 4.1.1, JSEP now specifies that the default RTCP multiplexing policy MUST be "require". 

We have enough data now to be confident that this change should only affect a small number of WebRTC connections.
 
Project Member Comment 1 by deadbeef@webrtc.org, Nov 12 2016
Just to note, here's a bug for changing the default in Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=659035

But we should change the default in the native library as well.
Project Member Comment 3 by bugdroid1@chromium.org, Dec 21 2016
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3291edb6105e4f7e39a0b4e81da9c24e234ad185

commit 3291edb6105e4f7e39a0b4e81da9c24e234ad185
Author: zhihuang <zhihuang@chromium.org>
Date: Wed Dec 21 00:47:17 2016

Change the default rtcp mux policy from negotiate to require.

After monitoring the UMA stats, the plan is to change the default rtcp mux policy from negotiated to require.
According to the UMA data in 28 days, 99.96% users choose the default value of rtcp mux policy which means nearly all the users who are using "negotiate" policy would be affected by this change. Because among all the users with media, only 3%  disabled the rtcp mux so it's not risky to make this change.

The UMA "SelectedRtcpMuxPolicy" is removed in this CL since it is only used to gauge the risk of this change.

BUG= webrtc:6030 

Review-Url: https://codereview.chromium.org/2055553003
Cr-Commit-Position: refs/heads/master@{#439955}

[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/chrome/test/data/webrtc/webrtc-simulcast.html
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/components/test_runner/mock_webrtc_peer_connection_handler.cc
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/components/test_runner/mock_webrtc_peer_connection_handler.h
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/content/renderer/media/rtc_peer_connection_handler.cc
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/content/renderer/media/rtc_peer_connection_handler.h
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/third_party/WebKit/Source/modules/peerconnection/RTCConfiguration.idl
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/third_party/WebKit/Source/modules/peerconnection/RTCPeerConnection.cpp
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/third_party/WebKit/public/platform/WebRTCConfiguration.h
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/third_party/WebKit/public/platform/WebRTCPeerConnectionHandler.h
[modify] https://crrev.com/3291edb6105e4f7e39a0b4e81da9c24e234ad185/tools/metrics/histograms/histograms.xml

Project Member Comment 4 by deadbeef@chromium.org, Dec 23 2016
Status: Verified
Project Member Comment 5 by anatolid@webrtc.org, Jan 11 2017
Labels: M-57
Sign in to add a comment