[webrtc-pc] RTCRtpParameters.codec matching is probably too strict (#2987)

docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCRtpParameters.codec matching is probably too strict ==
Let's say this is one of the codecs returned by getCapabilities, and JS sets a sender's RTCRtpParameters.codec to it before negotiation.

`{
   mimeType: 'video/vp8',
   clockRate: 90000,
   sdpFmtpLine: 'max-fs=12288;max-fr=60'
}`

Then, suppose the remote side's fmtp for vp8 looks like this, because it only wants to receive 30 frames per second (instead of the default of 60):

`a=fmtp:120 max-fs=12288;max-fr=30`

This results in the following entry in RTCRtpParameters.codecs:

`{
   mimeType: 'video/vp8',
   clockRate: 90000,
   sdpFmtpLine: 'max-fs=12288;max-fr=30',
   payloadType: 120
}`

The **codec dictionary match** algorithm says these do not match, despite the fact that the negotiation worked just fine for vp8. Most fmtp parameters are negotiable in this way. I get the impression that a failure to match here is not the intent.



Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2987 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 19 August 2024 16:19:43 UTC