- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Feb 2023 08:51:51 +0000
- To: public-webrtc-logs@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-extensions: == Do we need a control API for RTCP feedback mechanisms? == When hunting an unrelated problem, I came across the need to check whether or not certain RTCP feedback mechanisms (nack, rrtr, transport-cc) were turned on. It turned out that in order to do this, I had to do SDP inspection or C++ APIs; I would have to do the same thing to affect them. Do we have an use case where it makes sense to expose an API to turn these mechanisms on and off? (For extra credit: turn on and off feedback mechanisms that are transport-wide rather than codec-dependent) Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/143 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 February 2023 08:51:53 UTC