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

PRIORITY and Stream ID space #73

Closed
MikeBishop opened this issue Dec 5, 2016 · 1 comment
Closed

PRIORITY and Stream ID space #73

MikeBishop opened this issue Dec 5, 2016 · 1 comment
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@MikeBishop
Copy link
Contributor

The current PRIORITY frame has 31 bits to reference the dependent stream. We'd need to either do some weird dancing (omit one of the bits that can be inferred?), change the layout of PRIORITY to match QUIC's stream space size, or restrict the mapping to use a subset of QUIC streams.
@MikeBishop
Copy link
Contributor Author

Fixed in the current draft -- PRIORITY now has 32-bits and a clear field to expand if QUIC does.

@mnot mnot added the design An issue that affects the design of the protocol; resolution requires consensus. label Apr 19, 2017
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mnot @MikeBishop