W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2023

Re: [webrtc-extensions] Do we need a control API for RTCP feedback mechanisms? (#143)

From: bdrtc via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 Feb 2023 10:14:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1447913214-1677579240-sysbot+gh@w3.org>
As webrtc app developer, it's easy to see whether or not certain RTCP were turned on/off by analize default sdp.
But when the user want to turn on or off a certain rtcp feature, it is inconvenient (sdp munging),
so to add a control api is more convenient, then, what level api will you want?
maybe we should consider

1)media type level:
user may want disable audio tcc/others but open for video.
2)media direction:
user may want use remb rtcp in media send direction but use tcc in media receive direction.

-- 
GitHub Notification of comment by bdrtc
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/143#issuecomment-1447913214 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 10:14:04 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:20:00 UTC