- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Nov 2023 09:26:08 +0000
- To: public-webrtc-logs@w3.org
Historically, features have been shipped via SDP modifications rather than APIs. The API side of things have been playing catch-up, e.g. [setCodecPreferences()](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-setcodecpreferences) to allow modifying codecs that way instead of "[SDP munging](https://webrtc.github.io/samples/src/content/peerconnection/munge-sdp/)" or [modifying header extensions to negotiating in the extension spec](https://w3c.github.io/webrtc-extensions/#rtp-header-extension-control). So the list of reasons for SDP munging is quite small these days, but I'm not sure all holes have been plugged just yet. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2907#issuecomment-1798118415 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 November 2023 09:26:10 UTC