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

HTTP/3 doesn't mandate RFC8470 compliance #2432

Closed
MikeBishop opened this issue Feb 7, 2019 · 0 comments
Closed

HTTP/3 doesn't mandate RFC8470 compliance #2432

MikeBishop opened this issue Feb 7, 2019 · 0 comments
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus. proposal-ready An issue which has a proposal that is believed to be ready for a consensus call.

Comments

@MikeBishop
Copy link
Contributor

Since QUIC provides 0-RTT support, it really should.
@MikeBishop MikeBishop added design An issue that affects the design of the protocol; resolution requires consensus. -http labels Feb 7, 2019
@MikeBishop MikeBishop mentioned this issue Feb 7, 2019
Closed
@martinthomson martinthomson mentioned this issue Feb 7, 2019
Merged
@martinthomson martinthomson added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Feb 26, 2019
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. proposal-ready An issue which has a proposal that is believed to be ready for a consensus call.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @MikeBishop