From 9eac7301d3a964085ecb07652c69b04e75efe535 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Sun, 10 Jan 2021 22:09:37 -0800 Subject: [PATCH] Finesse relationship of resumption and 0-RTT Resumption is not quite the basis of 0-RTT, since it is also allowed to pre-provision an external PSK and other parameters and do 0-RTT that way. This also allows a rewording to avoid implying that 0-RTT would need to be enabled by configuration, since it is supposed to just be "on by default". Fixes: #4477 --- draft-ietf-quic-tls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-tls.md b/draft-ietf-quic-tls.md index 665a7880c1..8ca4d880b5 100644 --- a/draft-ietf-quic-tls.md +++ b/draft-ietf-quic-tls.md @@ -684,8 +684,8 @@ of type PROTOCOL_VIOLATION. QUIC can use the session resumption feature of TLS 1.3. It does this by carrying NewSessionTicket messages in CRYPTO frames after the handshake is -complete. Session resumption is the basis of 0-RTT, but can be used without -also enabling 0-RTT. +complete. Session resumption can be used to provide 0-RTT, and can also be +used when 0-RTT is disabled. Endpoints that use session resumption might need to remember some information about the current connection when creating a resumed connection. TLS requires