- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 16:32:51 +0000
- To: public-webrtc-logs@w3.org
> ... fmtp in the capabilities differs even slightly from what the remote puts in its SDP, we won't try to honor that .codec setting because it doesn't match. I don't believe the spec says what to do here. The codec dictionary algorithm is only used to validate JS inputs AFAICT. All it says about it seems inferred here: _"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."_ IOW, there's no RTP stream "selecting" algorithm. The purpose seems to be to choose between _"negotiated codecs"_, i.e. `parameters.codec` exists in `parameters.codecs` as an invariant. So for people who prefer strict APIs it is tempting to limit inputs to getParameters().codecs. But I suppose even that set may change after renegotiation, so we'd still need to clarify what to do when that invariant breaks. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2987#issuecomment-2307426533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 16:32:52 UTC