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

Fixed handshake key deadlock issue #3093

Closed
wants to merge 1 commit into from
Closed

Fixed handshake key deadlock issue #3093

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 5 additions & 4 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -384,14 +384,15 @@ perspective of the endpoint in question.
### Handshake Confirmed {#handshake-confirmed}

In this document, the TLS handshake is considered confirmed at an endpoint when
the following two conditions are met: the handshake is complete, and the
endpoint has received an acknowledgment for a packet sent with 1-RTT keys.
This second condition can be implemented by recording the lowest packet number
the following three conditions are met: the handshake is complete, the
endpoint has received an acknowledgment for a packet sent with 1-RTT keys, and
the endpoint has received an ack-eliciting packet sent with 1-RTT keys.

The second condition can be implemented by recording the lowest packet number
sent with 1-RTT keys, and the highest value of the Largest Acknowledged field
in any received 1-RTT ACK frame: once the latter is higher than or equal to the
former, the handshake is confirmed.


### Sending and Receiving Handshake Messages

In order to drive the handshake, TLS depends on being able to send and receive
Expand Down