Re: [webrtc-extensions] Header extension: direction woes and renames (#141)

I do not think we need `getDefaultHeaderExtensions`.
`getHeaderExtensionsToNegotiate` will always list the extensions the UA supports one way or another.

The direction describes the desired negotiation status.  This means that once we go from sendrecv to stopped we no longer know that we can go back to sendrecv. But we don't need that, why would the UA include an extension that can't be set to sendrecv in the set?
(csrc-audio-level might be a counterexample, it does not make sense for the browser to send but if as dev you modify it first to stopped and then 'on' again why do you expect this to work even? We can still reject an invalid modification attempt))

GitHub Notification of comment by fippo
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Friday, 3 February 2023 13:45:48 UTC