- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 13:46:03 +0000
- To: public-webrtc-logs@w3.org
> Agreed, do you know why this was phrased as is in JSEP in the first place? "Backward compat" probably and data channels were not as ubiquitous nine years ago as they are today. The bundle-tagged m-line getting rejected is still rare in practice but we do have both transceiver.stop and setCodecPreferences which make it something that needs to be dealt with. > Would having an IETF document describing this update to JSEP be overkill? Yes. I have a bunch of [minor issues with JSEP](https://github.com/rtcweb-wg/jsep/issues) but none of them warrants a -ter yet. https://w3c.github.io/webrtc-extensions/#rtp-header-extension-control-modifications shows how to do it. @dontcallmedom can you move the issue please? -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3072#issuecomment-3210684297 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 13:46:04 UTC