- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Nov 2023 18:55:10 +0000
- To: public-webrtc-logs@w3.org
aboba has just created a new issue for https://github.com/w3c/webrtc-rtptransport: == SDP "Bumper lanes" == What if a developer only wants to customize audio but not video? We have discussed allowing applications to access `RTCRtpReceiver.rtpTransport` and `RTCRtpSender.rtpTransport`. The question is what restrictions are placed on these send/receiver-specific RtpTransports by SDP: Unnegotiated PT? Easy to check Invalid Payload? Not easy to check Unnegotiated Header Extension ID? Easy Invalid Header Extension Value? Not Easy Unnegotiated SSRC? MIDs allow any Unnegotiated MID/RID? Not too hard Unnegotiated RTCP type? What if it's custom? All the m-lines are recvonly/inactive? Easy Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/10 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 November 2023 18:55:12 UTC