- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Apr 2024 23:01:04 +0000
- To: public-webrtc-logs@w3.org
Looking at receive codecs for sendrecv or recvonly m-lines makes some sense, even though it violates a SHOULD in [RFC 3264 Section 5.1](https://www.rfc-editor.org/rfc/rfc3264.html#page-6): > For a sendonly stream, the offer SHOULD indicate those formats the offerer is willing to send for this stream. For a recvonly stream, the offer SHOULD indicate those formats the offerer is willing to receive for this stream. For a sendrecv stream, the offer SHOULD indicate those codecs that the offerer is willing to send and receive with. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2937#issuecomment-2067375705 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:01:05 UTC