- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Feb 2024 10:21:34 +0000
- To: public-webrtc-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-pc: == Existing setCodecPreferences NOTE is wrong and should be deleted == The second NOTE under [setCodecPreferences](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-setcodecpreferences) says: > NOTE > Due to a recommendation in [[SDP](https://w3c.github.io/webrtc-pc/#bib-sdp)], calls to [createAnswer](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-createanswer) SHOULD use only the common subset of the codec preferences and the codecs that appear in the offer. For example, if codec preferences are "C, B, A", but only codecs "A, B" were offered, the answer should only contain codecs "B, A". However, [[RFC8829](https://w3c.github.io/webrtc-pc/#bib-rfc8829)] ([section 5.3.1.](https://www.rfc-editor.org/rfc/rfc8829#section-5.3.1)) allows adding codecs that were not in the offer, so implementations can behave differently. This does not advocate what we want for the unidirectional use case and I can't find a justification for it. I think it's probably based on a misunderstanding about the [difference between preferences and PT mappings](https://github.com/w3c/webrtc-pc/issues/2932). Proposal: Delete this note. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2933 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 February 2024 10:21:36 UTC