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

Make Handshake packet use more explicit #1368

Merged
merged 1 commit into from May 22, 2018
Merged

Make Handshake packet use more explicit #1368

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
5 changes: 5 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -640,6 +640,11 @@ A Handshake packet uses long headers with a type value of 0x7D. It is
used to carry acknowledgments and cryptographic handshake messages from the
server and client.

A server sends its cryptographic handshake in one or more Handshake packets in
response to an Initial packet if it does not send a Retry packet. Once a client
has received a Handshake packet from a server, it uses Handshake packets to send
subsequent cryptographic handshake messages and acknowledgments to the server.

The Destination Connection ID field in a Handshake packet contains a connection
ID that is chosen by the recipient of the packet; the Source Connection ID
includes the connection ID that the sender of the packet wishes to use (see
Expand Down