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

Stronger migration handshake #2370

Merged
merged 8 commits into from Jul 8, 2019
Merged

Stronger migration handshake #2370

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
ef52e69
State requirement that clients must wait until ACK of 1-RTT
huitema Jan 27, 2019
e449a44
Update the proposed migration text based on comments.
huitema Jan 27, 2019
cdaf4ff
Add handshake completion section so we can have a single reference.
huitema Jan 28, 2019
4b096a1
Per Tokyo interop: editors will complete the section "handshake compl…
huitema Feb 1, 2019
3a11ef0
Merge pull request #12 from quicwg/master
huitema Jun 5, 2019
7312d63
Merge pull request #13 from huitema/master
huitema Jun 5, 2019
23bacec
Reference "handshake confrmed" for connection migration.
huitema Jun 5, 2019
0cefaa1
Whitespace edits
martinthomson Jun 11, 2019
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
17 changes: 1 addition & 16 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1534,22 +1534,7 @@ a different codepoint.

### Handshake Completion {#handshake-completion}

The connection establishment handshake concludes when both parties have
successfully agreed on the protocol version and on encryption keys, and
have obtained insurance that all necessary Initial and Handshake messages
have been properly received by their peers, as defined in {{QUIC-TLS}}.

For the server, this is achieved when the TLS stack informs the
transport that the session establishment is complete, and that the
1-RTT receive keys can now be used, as indicated in section 4.1.3 of
{{QUIC-TLS}}.

For the client, this is achieved after the 1-RTT keys become available
when the server acknowledges either the client's Handshake message carrying
the last element of the Crypto Stream or an 1-RTT message sent by the client.
Waiting for either of these events allows the client to verify the
completion of the handshake even in cases where the Handshake
acknowledgement is lost.
TBD

# Address Validation

Expand Down