Abstract
- Stands for Quick UDP Internet Connections
- Think of QUIC as being similar to TCP+TLS+HTTP 2.0 implemented on UDP (Like TCP 2.0)
- Built on top of UDP but the mechanism is based on TCP
- Come with Zero Round Trip Time Resumption (0-RTT)
Why not build it on top of TCP?
We can’t change TCP in the same way we change HTTP to solve the TCP Head-of-Line Blocking issue, because modifying TCP requires changes to the kernel codes, which is much harder than changing a browser codes.
Tool
QUIC Handshake
- Integrating TCP Handshake with TLS Handshake into QUIC Handshake
QUIC Stream
- Introduce HTTP Stream in the transport layer
- Abstracting HTTP Request/HTTP Response into QUIC Frame
Important
Solves TCP Head-of-Line Blocking issue.
QUIC Frame
- Similar to the HTTP Frame, there isn’t HTTP frame in QUIC