You can't carry CCS anyway

quicwg · May 10, 2020 · 6a4c95e · 6a4c95e
1 parent 3a633d8
commit 6a4c95e
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/draft-ietf-quic-tls.md b/draft-ietf-quic-tls.md
@@ -1641,10 +1641,10 @@ ClientHello and ServerHello, then sending a change_cipher_spec record. Both
 field and record carry no semantic content and are ignored.
 
 This mode has no use in QUIC as it only applies to middleboxes that interfere
-with TLS over TCP. A client MUST NOT request the use of the TLS 1.3
-compatibility mode. A server SHOULD treat the receipt of a TLS ClientHello that
-with a non-empty legacy_session_id field as a connection
-error of type PROTOCOL_VIOLATION.
+with TLS over TCP. QUIC also provides no means to carry a change_cipher_spec
+record. A client MUST NOT request the use of the TLS 1.3 compatibility mode. A
+server SHOULD treat the receipt of a TLS ClientHello that with a non-empty
+legacy_session_id field as a connection error of type PROTOCOL_VIOLATION.
 
 
 # Security Considerations