From dc9d7ebdb2f14409a4a547bd0605f2b56814f050 Mon Sep 17 00:00:00 2001 From: Kazuho Oku Date: Wed, 26 Jun 2019 09:32:45 +0900 Subject: [PATCH] Remove stale text that forbids the use of TLS records carrying early data. As of -12, TLS records are not used in QUIC (TLS handshake messages are directly transmitted instead), and therefore it is impossible in QUIC to transmit early data using the mechinery provided by TLS. --- draft-ietf-quic-tls.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/draft-ietf-quic-tls.md b/draft-ietf-quic-tls.md index de7e0e3ee5..577e2ef1f3 100644 --- a/draft-ietf-quic-tls.md +++ b/draft-ietf-quic-tls.md @@ -613,10 +613,6 @@ by the "initial_max_data" transport parameter supplied by the server. A client MUST treat receipt of a NewSessionTicket that contains an "early_data" extension with any other value as a connection error of type PROTOCOL_VIOLATION. -Early data within the TLS connection MUST NOT be used. As it is for other TLS -application data, a server MUST treat receiving early data on the TLS connection -as a connection error of type PROTOCOL_VIOLATION. - ## Rejecting 0-RTT