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

Issue metadata

Status: Verified
Last visit > 30 days ago
Closed: Dec 2016
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Issue 6030: Change default RTCP mux policy to "require"

Reported by, Jun 22 2016 Project Member

Issue description

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.

Comment 1 by, Nov 12 2016

Project Member
Just to note, here's a bug for changing the default in Chromium:

But we should change the default in the native library as well.

Comment 3 by, Dec 21 2016

Project Member
The following revision refers to this bug:

commit 3291edb6105e4f7e39a0b4e81da9c24e234ad185
Author: zhihuang <>
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 

Cr-Commit-Position: refs/heads/master@{#439955}


Comment 4 by, Dec 23 2016

Project Member
Status: Verified (was: Assigned)

Comment 5 by, Jan 11 2017

Project Member
Labels: M-57

Sign in to add a comment