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.

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

transport: tls 5.2.2 is now 5.3.2 #1279

Merged
merged 1 commit into from
Apr 10, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -711,7 +711,7 @@ connection ID to vary in length and still be used by the load balancer.
The very first packet sent by a client includes a random value for Destination
Connection ID. The same value MUST be used for all 0-RTT packets sent on that
connection ({{packet-protected}}). This randomized value is used to determine
the handshake packet protection keys (see Section 5.2.2 of {{QUIC-TLS}}).
the handshake packet protection keys (see Section 5.3.2 of {{QUIC-TLS}}).

A Version Negotiation ({{packet-version}}) packet MUST use both connection IDs
selected by the client, swapped to ensure correct routing toward the client.
Expand Down