- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Apr 2024 00:07:11 +0000
- To: public-webrtc-logs@w3.org
@rshpount As we've [discussed on the RTCWEB mailing list](https://mailarchive.ietf.org/arch/msg/rtcweb/w_jHX-U8HkGtwZD6qftO8vBub10/), JSEPbis (now [RFC 9429](https://www.rfc-editor.org/rfc/rfc9429.html)) Section 4.2.6 is being interpreted to only check support for receive but not sending codecs, on both recvonly and sendrecv m-lines. So that is what would allow a receive-only codec to be provided in an Offer on a sendrecv m-line. As you point out, that is not consistent with the SHOULDs in RFC 3264 Section 5.1. So the question is: 1. Is RFC 9429 Section 4.2.6 in error (or at least requiring some additional context)? 2. If so, should we file an errata? -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2937#issuecomment-2071151295 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 April 2024 00:07:12 UTC