- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Nov 2024 14:55:03 +0000
- To: public-webrtc-logs@w3.org
> if you want to go this route you will also need to take care of [RFC6184](https://www.rfc-editor.org/rfc/rfc6184#section-8.1)s level-asymmetry-allowed, no? No this is just about the codec matching algorithm used to sanity check input to setParameters/setCodecPreferences, what is actually negotiated based on this is defined somewhere else. As for sending the selected codec, the description is kind of vague, [RTCRtpEncodingParmaters.codec](https://w3c.github.io/webrtc-pc/#dom-rtcrtpencodingparameters-codec) just says: > Optional value selecting which codec is used for this encoding's RTP stream. If absent, the user agent can chose to use any negotiated codec. And [setParameters](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-setparameters) just says: > [In parallel](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel), configure the media stack to use parameters to transmit sender.[[[SenderTrack]]](https://w3c.github.io/webrtc-pc/#dfn-sendertrack). So it's just "codec used for selecting what to send", we might want to create an issue about clarifying not to send greater than the level-id that was negotiated, but that seems more like an editorial note. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/3023#issuecomment-2491449747 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 November 2024 14:55:03 UTC