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

Signal from TLS that this needs to be a Retry #1061

Closed
martinthomson opened this issue Jan 22, 2018 · 0 comments
Closed

Signal from TLS that this needs to be a Retry #1061

martinthomson opened this issue Jan 22, 2018 · 0 comments
Assignees
@martinthomson
Labels
-tls 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

@martinthomson
Copy link
Member

When the TLS stack produces a retry, then it should signal to the QUIC stack that it is a retry. This would allow QUIC to construct the right sort of packet to put its bytes into. It also allows a QUIC server to do things like dump state.
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -tls labels Jan 22, 2018
@martinthomson martinthomson self-assigned this Mar 14, 2018
martinthomson added a commit that referenced this issue Mar 14, 2018
@martinthomson
Create a signal about HelloRetryRequest
6a98621 
Closes #1061.
@martinthomson martinthomson mentioned this issue Mar 14, 2018
Merged
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martinthomson martinthomson

Labels
-tls 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
@martinthomson @mnot