Re: [quicwg/base-drafts] TLS application data isn't possible (#3043)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



>  
 QUIC takes the unprotected content of TLS handshake records as the content of
 CRYPTO frames. TLS record protection is not used by QUIC. QUIC assembles
 CRYPTO frames into QUIC packets, which are protected using QUIC packet
 protection.
 
+QUIC is only capable of conveying TLS handshake records in CRYPTO frames.  TLS
+alerts are turned into QUIC CONNECTION_CLOSE error codes; see {{tls-errors}}.
+TLS application data and other message types cannot be carried by QUIC at any
+encryption level and can be treated as an error if they are received from the

This is a clarification of fact, that a TLS stack can never return application data, unless there is a bug in the TLS stack or in the way the QUIC stack uses the TLS stack.

Therefore I think that "can be treated as an error" is fine. Changing it to "is an error" would be fine too.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3043#discussion_r325400514