Re: [webrtc-pc] Applying a remote offer with unsupported codecs results in stale transceiver (#2927)

Creating initial answers says to reject the m= section if "There is no offered media format that is both supported and, if applicable, allowed by codec preferences".

This makes sense to me, but IIUC the argument here is that since stopping the transceiver is inevitable, we might as well do it earlier (at `setRemoteDescription(offer)` as opposed to `setLocalDescription(answer)`)?

Is there any benefit to doing it earlier? I'm biased towards not changing the spec if things are already working correctly. Also changing these kinds of things can have unintended consequences, for example the "rollback" steps reference trying to find a corresponding transceiver for the m= section and create one if it doesn't exist, so if we stop the transceiver earlier then we'd end up creating a second transceiver for the m= section as part of rollback only to stop it later? Not sure this reading is correct but this is the kind of thing I'm worried about.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2927#issuecomment-2388518513 using your GitHub account


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

Received on Wednesday, 2 October 2024 12:27:11 UTC