From f3446939a34945fe7bae89a0bf792b6656b66118 Mon Sep 17 00:00:00 2001 From: EKR Date: Tue, 17 Oct 2017 08:58:18 -0700 Subject: [PATCH] Connection ID is big endian --- draft-ietf-quic-tls.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/draft-ietf-quic-tls.md b/draft-ietf-quic-tls.md index ab069b8f15..83e09f1bca 100644 --- a/draft-ietf-quic-tls.md +++ b/draft-ietf-quic-tls.md @@ -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