What does each of these experimental goog-RTCPeerConnectionConstraints do?

Question

From various examples, sites, forums, discussions, and source codes, I have compiled this list of Google’s RTCPeerConnection experimental limitations. What does each of them do in the context of RTCPeerConnection WebRTC?

peerConnectionConstraints: optional: [ #goog experimental { googIPv6: true } { googImprovedWifiBwe: true } { googDscp: true } { googSuspendBelowMinBitrate: true } { googScreencastMinBitrate:400 } { googCombinedAudioVideoBwe: true } { googCpuOveruseDetection: true } { googCpuOveruseEncodeUsage: true } { googCpuUnderuseThreshold: 55 } { googCpuOverUseThreshold: 85 } ] 

Answer 1

Most of these options are not documented. Some have been used for Google products such as Hangouts.

googIPv6 - allows you to support IPv6 for Chrome (should also work in the latest Firefox)

googImprovedWifiBwe . Chrome has an algorithm for estimating bandwidth, and this flag allows you to improve (but experimental) the version of the algorithm. In the latest version of Chrome, this flag is enabled by default, the experiment was successful.

googDscp - allows DSCP

googScreencastMinBitrate - Used by the Hangouts app. Sets the minimum bitrate for shielding.

googCpuOveruseDetection - if enabled, Chrome will reduce the quality of outgoing video and video resolution

googCpuUnderuseThreshold - minimum CPU load (percent) used in conjunction with googCpuOveruseDetection

googCpuOverUseThreshold - maximum processor (percent) used in conjunction with googCpuOveruseDetection

googCpuOveruseEncodeUsage - don't know

googSuspendBelowMinBitrate - the minimum bit to consider the session is alive (not sure)

googCombinedAudioVideoBwe - don't know