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

Do we need end_of_early_data #12

Open
martinthomson opened this issue Nov 7, 2016 · 1 comment
Open

Do we need end_of_early_data #12

martinthomson opened this issue Nov 7, 2016 · 1 comment

Comments

@martinthomson
Copy link
Owner

KEY_PHASE might be enough. Once you decrypt with 1-RTT keys, you know that 0-RTT is over.

If we decide that we do need it, then it is on the TLS stream (1).

@martinthomson
Copy link
Owner Author

Thinking more... The TLS implementation might be easier if we send it on stream 1. The TLS 0-RTT handling will be expecting to see EOED before it moves to handling the client's second flight of handshake messages. We can still avoid the complication of having it interact with QUIC, relying instead on the KEY_PHASE bit there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant