W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2020

[webrtc-nv-use-cases] do we need RTCCbrStatus? (#57)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Jan 2020 21:53:15 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-545959254-1578347593-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/webrtc-nv-use-cases:

== do we need RTCCbrStatus? ==
Moved from https://github.com/w3c/webrtc-pc/issues/2301

Do we need RTCCbrStatus for [opus cbr](https://tools.ietf.org/html/rfc7587#section-3.1.2)?
The description would be somewhat similar  to the [dtx one](https://w3c.github.io/webrtc-pc/#dom-rtcrtpencodingparameters-dtx) (which is marked as at-risk?!)

Since @aboba asked: even without an API it is still possible to munge the SDP to enable this.
This is second form munging, i.e. on the signaling channel before setRemoteDescription.
Like for dtx we don't have an actual API to tell the sender to create an offer and negotiate it.

Please view or discuss this issue at https://github.com/w3c/webrtc-nv-use-cases/issues/57 using your GitHub account
Received on Monday, 6 January 2020 21:53:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:51 UTC