Comparing TCP and QUIC (2022)
Geoff Huston compares TCP and QUIC protocols in the October 2022 ISP Column. QUIC is seen as a transformative protocol with enhanced privacy, speed, and flexibility, potentially replacing TCP on the Internet. QUIC offers improved performance for encrypted traffic and independent transport control for applications.
Read original article
In the October 2022 ISP Column, Geoff Huston discusses the differences between the traditional TCP protocol and the newer QUIC protocol. While some view QUIC as a mere refinement of TCP, Huston argues that QUIC represents a significant shift in transport capabilities, offering enhanced communication privacy, session control integrity, and flexibility. He highlights that QUIC operates on a different communication model, making it more versatile for various application behaviors and faster than TCP. Huston predicts that QUIC may eventually replace TCP on the public Internet due to its advanced features. TCP, on the other hand, is described as a bilateral full-duplex protocol that ensures reliability, sequencing, and flow control. The article delves into the technical aspects of TCP, including its stream protocol nature, connection setup through a three-way handshake, sliding window mechanism, and adaptive flow control. Additionally, the article briefly touches on the integration of Transport Layer Security (TLS) with TCP. Moving on to QUIC, the article explains how QUIC addresses issues with TCP and TLS, offering improved transport performance for encrypted traffic, faster session setup, and avoiding TCP ossification. QUIC is described as encapsulated and encrypted TCP over UDP, providing advantages such as concealing transport flow control parameters from the network and enabling applications to control transport services independently. The article also outlines the structure of QUIC connections and how they handle changes in addressing to ensure packet delivery integrity.
Related
Timeliness without datagrams using QUIC
The debate between TCP and UDP for internet applications emphasizes reliability and timeliness. UDP suits real-time scenarios like video streaming, while QUIC with congestion control mechanisms ensures efficient media delivery.
Beyond bufferbloat: End-to-end congestion control cannot avoid latency spikes
End-to-end congestion control methods like TCP and QUIC face challenges in preventing latency spikes, especially in dynamic networks like Wi-Fi and 5G. Suggestions include anticipating capacity changes and prioritizing latency-sensitive traffic for a reliable low-latency internet.
QUIC File Transfer Service, a CLI and srv for transferring large files
A QUIC File Transfer Service CLI and server use the QUIC Protocol for fast large file transfers. It supports stream multiplexing, 0-RTT connections, MD5 checksums, and includes server/client implementations with setup guidance.
Httpwtf?
HTTP has hidden features like cache directives, trailers for metadata, and 1XX codes. Websockets bypass CORS, X-* headers allow custom extensions. Despite quirks, HTTP is vital for client-server communication.
Why aren't we using SSH for everything? (2015)
SSH, known for secure server access, can extend to chat rooms, APIs, and file serving. Despite lacking HTTP/2 features, its encryption and authentication benefits raise questions on underutilization.
3 commentsI've recently heard QUIC referred to as "SCTP over UDP".
Related
Timeliness without datagrams using QUIC
The debate between TCP and UDP for internet applications emphasizes reliability and timeliness. UDP suits real-time scenarios like video streaming, while QUIC with congestion control mechanisms ensures efficient media delivery.
Beyond bufferbloat: End-to-end congestion control cannot avoid latency spikes
End-to-end congestion control methods like TCP and QUIC face challenges in preventing latency spikes, especially in dynamic networks like Wi-Fi and 5G. Suggestions include anticipating capacity changes and prioritizing latency-sensitive traffic for a reliable low-latency internet.
QUIC File Transfer Service, a CLI and srv for transferring large files
A QUIC File Transfer Service CLI and server use the QUIC Protocol for fast large file transfers. It supports stream multiplexing, 0-RTT connections, MD5 checksums, and includes server/client implementations with setup guidance.
Httpwtf?
HTTP has hidden features like cache directives, trailers for metadata, and 1XX codes. Websockets bypass CORS, X-* headers allow custom extensions. Despite quirks, HTTP is vital for client-server communication.
Why aren't we using SSH for everything? (2015)
SSH, known for secure server access, can extend to chat rooms, APIs, and file serving. Despite lacking HTTP/2 features, its encryption and authentication benefits raise questions on underutilization.