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.

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

Conflict between SETTINGS_NUM_PLACEHOLDERS and SETTINGS_ENABLE_CONNECT_PROTOCOL #2443

Closed
MikeBishop opened this issue Feb 8, 2019 · 0 comments
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus.

Comments

@MikeBishop
Copy link
Contributor

Checking the HTTP/2 IANA registry, it seems we have a clash on 0x8 due to RFC 8441 - WebSocket over HTTP/2. I think its reasonable that someone might write a WebSocket over HTTP/3 extension and reusing the code point would be nice. Can we move NUM_PLACEHOLDERS to 0x9 and leave 0x8 open?

Originally posted by @LPardue in #2437

@MikeBishop MikeBishop added design An issue that affects the design of the protocol; resolution requires consensus. -http labels Feb 8, 2019
LPardue added a commit to LPardue/base-drafts that referenced this issue Mar 20, 2019
Fixes quicwg#2443.

Leave 0x8 open and unreserved so that some future extension document can use it for WebSockets (if they so wish).
MikeBishop pushed a commit that referenced this issue Mar 23, 2019
Fixes #2443.

Leave 0x8 open and unreserved so that some future extension document can use it for WebSockets (if they so wish).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus.
Projects
None yet
Development

No branches or pull requests

1 participant