- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jan 2024 13:42:57 +0000
- To: public-webrtc-logs@w3.org
There's also (from [RFC3264](https://www.ietf.org/rfc/rfc3264.txt)): > For streams marked as recvonly in the answer, the "m=" line MUST > contain at least one media format the answerer is willing to receive > with from amongst those listed in the offer. The stream MAY indicate > additional media formats, not listed in the corresponding stream in > the offer, that the answerer is willing to receive. > [...] For streams marked as sendrecv in the answer, > the "m=" line MUST contain at least one codec the answerer is willing > to both send and receive, from amongst those listed in the offer. So while we can add codecs we want to receive that were not present in the offer, it appears that what is offered cannot be entirely distinct either, as at least one codec needs to either be present in the offer or that is sendrecv-capable? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2888#issuecomment-1884875253 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 January 2024 13:42:59 UTC