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
0-RTT for client #466
Labels
Comments
All three issues are TLS 1.3, sigh. |
With handshake state:
The last 3 actions can be replaced with |
Minimal story:
Normal story:
|
Done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currenly, a client can send early data through
clientEarlyData
.This data must be decided in advance.
So, this can only be used for interoperability testing in a fixed scenario.
Ideally, it's nice that
sendData
can send early data while negotiating.quic
can do this because it is based on the multiple thread model.The receiver can receive packets while the sender is sending packets.
tls
is based on the single thread model.One approach is fork a thread to receive the server first flight after sending a client hello(CH):
R and W denote locks.
The text was updated successfully, but these errors were encountered: