search

w3c / webrtc-nv-use-cases

Use cases for WebRTC NV
https://w3c.github.io/webrtc-nv-use-cases/
Other
32 stars 13 forks source link

Control surface for header extensions #40

Closed aboba closed 5 years ago

aboba commented 5 years ago

Copied from Issue https://github.com/w3c/webrtc-pc/issues/2243

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 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.

@jonex

aboba commented 5 years ago

Aside from header extensions, there are is also RTCP-related info. So should in WebRTC 1.0, should we just have a setPreferences() method that covers everything?

aboba commented 5 years ago

With merger of PR 46, closing this issue.