- From: Roman Shpount via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Apr 2024 23:34:14 +0000
- To: public-webrtc-logs@w3.org
> It's ok because including a codec in an Offer on a recvonly or sendrecv m-line only requires the Offerer to be able to receive the codec; Including a receive-only codec in the sendrecv line is not ok. You need to, somehow, tell the answerer that the receive-only codec should not be removed from the answer and that another codec should present with a higher preference. If the answerer includes only this codec in the answer, that will force the offerer to send it, which it cannot do. If the answerer does not include the receive-only codec in the answer, then this codec cannot be used in the session since, according to RFC 3264, it should be released by the offerer. So, this is not a negotiation. It is going through signaling motions that only work if we already know the remote capabilities. -- GitHub Notification of comment by rshpount Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2937#issuecomment-2067393328 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 April 2024 23:34:15 UTC