- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Dec 2023 15:04:51 +0000
- To: public-webrtc-logs@w3.org
That's clever (having a=rtpmap contain all codecs you support, but the preferences could be a subset of the PTs). We still have the issue that the SDP answerer has no way of knowing the directional support of a codec that is listed in the a=rtpmap line, but it sounds like this is a limitation of SDP rather than a limitation of webrtc-pc APIs. So I think we can live with it: the app can easily check codec directionality support using `RTCRtpSender/Receiver.getCapabilities` and communicate those to the other endpoint if it so desires, but that would not be covered by SDP. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2888#issuecomment-1838836928 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 December 2023 15:04:53 UTC