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

0-RTT is still optional #3136

Closed
MikeBishop opened this issue Oct 23, 2019 · 1 comment · Fixed by #3138
Closed

0-RTT is still optional #3136

MikeBishop opened this issue Oct 23, 2019 · 1 comment · Fixed by #3138
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@MikeBishop
Copy link
Contributor

In Section 5.4, we say that one of the required operations on a connection is "enable 0-RTT".

@mikkelfj asks:

But why does an application need to be able to enable 0-RTT? Isn't 0-RTT optional at transport level, and more so at the app level?

The current text implies that implementations are required to support 0-RTT, which is not the case. It would be more correct to say that applications must be able to prevent early data from being offered on a connection, even if the implementation supports it.
@MikeBishop MikeBishop added -transport editorial An issue that does not affect the design of the protocol; does not require consensus. labels Oct 23, 2019
@MikeBishop
Copy link
Contributor Author

Alternately, the server section prefaces certain bullets with "If Early Data is supported, ...." That formulation might be used here as well.

Also, this section uses "0-RTT" in the client piece but "Early Data" in the server piece. Should be consistent.

martinthomson added a commit that referenced this issue Oct 23, 2019
@martinthomson
Applications need to disable or selectively reject 0-RTT
8b078aa 
Closes #3136.
@martinthomson martinthomson mentioned this issue Oct 23, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Applications need to disable or selectively reject 0-RTT quicwg/base-drafts
1 participant
@MikeBishop