- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Jan 2023 12:54:56 +0000
- To: public-webrtc-logs@w3.org
We do extend JSEP already [here](https://w3c.github.io/webrtc-extensions/#modifications-to-existing-procedures-0) The naming is confusing indeed. * getRtpHeaderExtensionsSupported() which returns a sequence of RTCRtpHeaderExtensionCapability. I have doubts this is the right model since it duplicates RTCRtpSender.getCapabilities (and the Receiver) while extending the data provided by stopped extensions. I'd prefer a [getCapabilities()](https://github.com/w3c/webrtc-extensions/issues/100#issuecomment-1110005582).headerExtensions * setRtpHeaderExtensions(headerExtensionsToNegotiate) to set what gets negotiated in an offer/answer. * headerExtensionsNegotiated() which lets you discover what was negotiated. IMO that is just a nice accessor for the `m=` section associated with the transceiver and extracting the information from the extmap so I have a slight preference to remove this. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/132#issuecomment-1396932200 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 January 2023 12:54:57 UTC