4 ms·
> QUIC is TLS-equivalent, not TCP-equivalent. From Wikipedia[1]: "QUIC improves performance of connection-oriented web applications that are currently using T
by rewmie 3y ago
> QUIC is TLS-equivalent, not TCP-equivalent.
From Wikipedia[1]:
"QUIC improves performance of connection-oriented web applications that are currently using TCP.[QUIC] is designed to obsolete TCP at the transport layer for many applications, thus earning the protocol the occasional nickname "TCP/2"."
Also taken from the wiki page:
"QUIC aims to be nearly equivalent to a TCP connection but with much-reduced latency."
Here is the only relevant bit regarding TLS:
"As most HTTP connections will demand TLS, QUIC makes the exchange of setup keys and supported protocols part of the initial handshake process. When a client opens a connection, the response packet includes the data needed for future packets to use encryption. This eliminates the need to set up the TCP connection and then negotiate the security protocol via additional packets."
[1] https://en.m.wikipedia.org/wiki/QUIC https://en.m.wikipedia.org/wiki/QUIC
- evgpbfhnr 3y agoThe RFCs for QUIC (RFC 9000 and RFC 9001) mandate encryption. Some random stackoverflow answer[1] claims there are implementations that ignore this and allow "QUIC without encryption", but I'd argue that it's not QUIC anymore -- in my opinion it'd be harmful to implement in the kernel. [1] https://stackoverflow.com/a/72828565/2332808 https://stackoverflow.com/a/72828565/2332808
- MerManMaid 3y agoPer the RFC, QUIC is literally defined as a transport protocol... Literally the first sentence of the overview is: "QUIC is a secure general-purpose transport protocol." More importantly, QUIC literally bakes in TLS into how it works which is a far cry away from replacing it. "The QUIC handshake combines negotiation of cryptographic and transport parameters. QUIC integrates the TLS handshake [TLS13], although using a customized framing for protecting packets."