W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2019

[webrtc-pc] Control surface for header extensions (#2243)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Wed, 31 Jul 2019 07:47:39 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-474988750-1564559258-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Control surface for header extensions ==
For codecs we have getCapabilities() for figuring out what is supported by the browser, setCodecPreferences() for controlling what to negotiate, and getParameters() to see what was actually negotiated. In addition, getStats() can tell you more details (such as if multiple codecs were negotiated, which one is being used right now).

Should we have a similar API for header extensions? There is already getParameter()'s [headerExtensions](https://w3c.github.io/webrtc-pc/#dom-rtcrtpparameters-headerextensions) for reading what RTP header extensions were negotiated, but there is no way to detect what is supported without trial and error, and worse yet, if you want to control which ones are negotiated you have to munge SDP.

I don't expect SDP munging to go away if we don't have APIs for things like this.

@jonex

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2243 using your GitHub account
Received on Wednesday, 31 July 2019 07:47:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:26 UTC