QUIC fixes this with independent streams: each HTTP request/response gets its own stream with its own ordering. A loss on stream A only blocks stream A. Streams B, C, D keep flowing.
You might ask: "Why not invent a brand-new transport protocol number at the IP layer?" Because the internet's middleboxes would drop unknown protocols. UDP is already universally allowed (it carries DNS!). So QUIC piggybacks on UDP as a "delivery truck" and rebuilds all of TCP's good features in encrypted user space. UDP gives you ports + checksum; QUIC adds back reliability, ordering, flow control, and congestion control.
Imagine you're moving 50 toys to a friend's house using one delivery truck, and the rule is "unload them strictly in order." If toy #1 falls off and has to be re-fetched, the driver won't unload toys #2–#50 either — everyone waits for toy #1. That's TCP.
Now imagine each toy rides in its own little go-kart on the same road. If one go-kart breaks down, the other 49 keep arriving. That's QUIC/HTTP3. And the go-karts use the ordinary road (UDP) that's open everywhere, instead of a fancy special road that guards keep blocking. Plus, you can switch from your bike to a car halfway (Wi-Fi to mobile data) and the go-karts still find you.
Dekho, HTTP/3 ka core idea simple hai: pehle HTTP TCP ke upar chalta tha, ab QUIC ke upar chalta hai, aur QUIC khud UDP ke upar baithta hai. TCP ka problem yeh tha ki woh saara data ek single ordered stream me bhejta hai — matlab agar ek chhota packet bhi kho gaya, toh uske baad ke saare bytes deliver nahi honge jab tak woh khoya packet wapas nahi aata. Web page me 50 objects ek saath load hote hain, toh ek loss poori connection ko freeze kar deta hai. Isko hum head-of-line blocking kehte hain.
QUIC isko fix karta hai independent streams se — har request ki apni alag line hai, toh ek stream ka loss baaki streams ko nahi rokta. Plus QUIC ka handshake fast hai: TCP+TLS me 2 round-trip lagte the, QUIC me sirf 1-RTT (aur returning user ke liye 0-RTT, yaani request data pehle hi packet me chala jaata hai). High-RTT mobile networks pe yeh bahut bada faayda hai.
Ab sawaal: UDP hi kyun? Kyunki internet ke beech me jo middleboxes (routers, firewalls) hote hain, woh naye-naye protocols ko drop kar dete hain, lekin UDP ko sab allow karte hain (DNS bhi UDP use karta hai). Toh QUIC UDP ko ek "delivery truck" ki tarah use karta hai aur TCP ke saare achhe features (reliability, ordering, congestion control) khud rebuild karta hai — woh bhi encrypted user-space me, taaki upgrade karna aasaan ho. Encryption (TLS 1.3) QUIC me mandatory hai.
Ek aur mast cheez: QUIC me Connection ID hota hai jo IP/port pe depend nahi karta, isliye jab tum Wi-Fi se mobile data pe switch karte ho, video stream nahi tutta — connection migrate ho jaati hai. Yaad rakhna: HTTP/3 ne HTTP ke meaning (GET, POST, headers, status codes) ko nahi badla, sirf neeche ka transport badla hai.
