Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

JSEP should refer to "header extensions to negotiate" rather than "supported header extensions" #1032

Closed
henbos opened this issue Apr 27, 2023 · 0 comments · Fixed by #1033
Closed

JSEP should refer to "header extensions to negotiate" rather than "supported header extensions" #1032

henbos opened this issue Apr 27, 2023 · 0 comments · Fixed by #1033

Comments

@henbos
Copy link

henbos commented Apr 27, 2023

The spec assumes you always want to negotiate everything you can, rather than whichever set of header extensions that you're interested in negotiating.

We should change the wording here, so that implementations are allowed to decide which ones to use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Draft PR for configuring RTP extensions rtcweb-wg/jsep
1 participant
@henbos