From 1a71021393c0f15d6a90a03a01918e4adb698f53 Mon Sep 17 00:00:00 2001 From: Peter Wu Date: Tue, 2 May 2017 19:46:34 +0200 Subject: [PATCH] PSK context for 0-RTT needs version number The 0-RTT key might differ between TLS versions (as demonstrated with the draft -20 changes). Be explicit about storing this version number since section 4.2.9 requires this information too. --- draft-ietf-tls-tls13.md | 1 + 1 file changed, 1 insertion(+) diff --git a/draft-ietf-tls-tls13.md b/draft-ietf-tls-tls13.md index 059529621..1c6f5e01d 100644 --- a/draft-ietf-tls-tls13.md +++ b/draft-ietf-tls-tls13.md @@ -1313,6 +1313,7 @@ the server and to encrypt the early data. When clients use a PSK obtained externally to send early data, then the following additional information MUST be provisioned to both parties: + * The TLS version number for use with this PSK * The cipher suite for use with this PSK * The Application-Layer Protocol Negotiation (ALPN) protocol, if any is to be used * The Server Name Indication (SNI), if any is to be used