Modern Web Transport

QUIC · HTTP/3 · WebRTC

1:00

How QUIC, HTTP/3, and WebRTC replaced the old TCP+TLS stack to eliminate handshake latency, head-of-line blocking, and high-latency peer-to-peer communication.

By the end, you can

Explain why the old TCP + TLS stack costs 2+ round trips before data flows.
Describe how head-of-line blocking works in HTTP/2 over TCP and why it was not fully solved there.
Explain what QUIC is, what it runs on top of, and why user-space implementation matters.
Distinguish 1-RTT and 0-RTT QUIC connection setup, including the replay risk of 0-RTT.
Explain how QUIC's independent streams eliminate transport-layer head-of-line blocking.
Define connection migration and explain why a Connection ID enables it.
Describe HTTP/3 as HTTP over QUIC, including QPACK compression and browser discovery.
Identify the three WebRTC browser APIs and what each provides.
Explain the roles of a signaling server, SDP, STUN, ICE, and TURN in establishing a WebRTC call.
State which encryption protocol protects WebRTC media (SRTP) versus data channels (DTLS).
Choose between HTTP/3 and WebRTC for a given application scenario.

Up next in Networking, Distributed Systems & Databases