Discover and read the best of Twitter Threads about #rfc9000
Most recents (1)
Day 4 of our deep dive into the freshly standardized #QUIC protocol is about one of its most innovative aspects: connection migration!
This is intended to allow #QUIC connections to survive network changes that are disruptive in TCP.
1/12 #RFC9000
This is intended to allow #QUIC connections to survive network changes that are disruptive in TCP.
1/12 #RFC9000
Take the "parking lot problem": you have WiFi on your phone inside, but switch to 4G when going to your car.
This switches networks and client IP/port, so all TCP connections are dropped and re-started, since they're only identified based on client+server IP+port (4-tuple). 2/12
This switches networks and client IP/port, so all TCP connections are dropped and re-started, since they're only identified based on client+server IP+port (4-tuple). 2/12
QUIC instead assigns each connection a unique Connection ID (CID) of 1-20 bytes.
By using the same CID even after switching networks, the server knows it's actually the same connection, even though the 4-tuple has changed. 3/12
By using the same CID even after switching networks, the server knows it's actually the same connection, even though the 4-tuple has changed. 3/12
