- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Feb 2024 16:13:02 +0000
- To: public-webrtc-logs@w3.org
I believe JSEP had a specific intention (but we should really nag the authors). If your initial offer included a codec that you were capable of sending but not receiving how would you signal that? > The "m=" line and corresponding "a=rtpmap" and "a=fmtp" lines MUST only include .. That covers the following scenario: A: H264-only offer B: H264-only answer (but might include additional codecs, unless sCP was used) B: H264 + VP8 offer Do we have tests for that? I doubt it but that is fixable. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2938#issuecomment-1941921871 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 February 2024 16:13:04 UTC