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

Connection ID is big endian #881

Closed
wants to merge 1 commit into from
Closed

Connection ID is big endian #881

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
3 changes: 3 additions & 0 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -665,6 +665,9 @@ connection ID. Specifically:
The HKDF for the cleartext packet protection keys uses the SHA-256 hash function
{{FIPS180}}.

As with other QUIC values, the client_connection_id is fed into HKDF-Extract
in network (big-endian) byte order.

The salt value is a 20 octet sequence shown in the figure in hexadecimal
notation. Future versions of QUIC SHOULD generate a new salt value, thus
ensuring that the keys are different for each version of QUIC. This prevents a
Expand Down