This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

Ping. Is this removal going to happen?

Usage of non-muxed RTCP is now around 2.5%. Peter, Harald, what do you suggest? That number still seems too large to ignore. But I also doubt it will get much lower by waiting longer.

Which usage is 2.5%, and of what?
Chrome usage? 2.5% of all PeerConnections?

I see it as 0.0000085% of all page loads, so by Chrome metrics, it's a very rarely-used feature. (Blink.UseCounter.Features RtcpMuxPolicyNegotiate).

If it's Chrome, we can send out an Intent to Deprecate and Remove, and add an UMA::CountDeprecated (which will print errors on the console) to the appropriate option handling function. Then wait a couple of Chrome cycles and reevaluate.

People sometimes react when given a deadline.

I see that we have been emitting a deprecation message already, so that didn't work. Did we leave the message on after we let the M62 deadline slip by?

Sorry for not clarifying; it's 2.5% of PeerConnections, and specifically those that actually use RTP/RTCP (not DataChannel-only connections).

And yes, the "will be removed no earlier than M62" deprecation message is still there.