QUIC: The Future of Internet Communication or a Dead End?

While much of our lives now takes place online, we rarely think about how everything actually works. In the background, when we open a website on our smartphone, countless actions occur that we neither notice nor control. Network packets are constantly being sent to the router and back to the device, even when we’re not actively doing anything online. Even when simply browsing a small web page, our devices exchange a significant amount of data with cell towers and other equipment.

In this article, we’ll discuss the QUIC network transmission protocol and how it may soon change the way we interact with web applications.

A Brief History of QUIC and Its Connection to Google

In the early 2010s, Google engineers were actively searching for ways to speed up and improve web applications. Not everyone had a stable, high-speed internet connection, which made navigating the web difficult. A potential solution was soon found, aiming to significantly optimize user interaction with web services.

In 2012, American software engineer Jim Roskind, then at Google, led a new internal project called Quick UDP Internet Connections (QUIC). The idea was to maximize the speed of the existing UDP (User Datagram Protocol) by adding security and congestion control features.

Network congestion typically refers to a decline in service quality that occurs when a network node or link carries more data than it can handle. Common consequences include queueing delays, packet loss, or blocking new connections. As congestion increases, network throughput decreases.

Extensive testing of QUIC showed promising results, but for various reasons, the technology remained experimental for many years and has yet to see widespread adoption. In the early 2020s, Google handed the project over to the Internet Engineering Task Force (IETF) for further standardization.

Currently, QUIC is supported to some extent in various web browsers and operating systems, but experts expect its adoption to grow rapidly in the near future.

What Are the Advantages and Disadvantages of QUIC?

QUIC is a significant step forward for the networking industry, but several factors may hold it back. Let’s look at the key advantages and possible drawbacks of the QUIC protocol.

Advantages

• Lower latency. Faster response times benefit real-time applications like video conferencing and online gaming.
• Improved efficiency under network congestion. Efficient handling and routing of network traffic, even under heavy loads, ensures smooth operation of all equipment.
• Enhanced security. Since security features are built directly into the protocol, QUIC can significantly improve the security of network packets.
• Multiple data streams simultaneously. Support for multiple data streams within a single connection allows applications to be more multitasking and efficient.
• Seamless reconnection when switching networks. When you switch from Wi-Fi to 5G, your connection resumes even faster than with TCP/UDP.

Disadvantages

• Full implementation takes time. As with any new technology or protocol, it may take years before QUIC becomes a universal international standard.
• Potential security issues. Since QUIC is built on UDP, firewalls may have difficulty inspecting network traffic for threats. Developers will need to implement new methods for tracking QUIC-based network packets in their firewalls.
• Increased development costs. QUIC is a relatively new and potentially more complex protocol, which may increase development costs.
• Potential compatibility issues. TCP is the most widely used protocol for many modern and older devices, so QUIC may not work everywhere.
• Fewer inspection options for network managers. Due to QUIC’s encryption, network managers may need more time to inspect and detect threats in real time. They must use firewalls with QUIC detection features and other methods to keep up with potential security threats.

What Is TCP and How Is It Used?

If you’ve ever tried to set a static IP address on your device or change DNS servers, you’ve probably seen options for configuring TCP/IPv4 or TCP/IPv6.

The Transmission Control Protocol (TCP) converts requested network data into packets and checks them for errors. The Internet Protocol (IP), in turn, addresses and correctly routes these packets to all connected devices on the network.

TCP/IP allows devices to connect to the Internet by assigning them unique IP addresses and letting the local network router identify them. The router can then send and receive data packets to and from the appropriate devices, creating a continuous stream of network traffic.

All of this, combined with various other protocols and MAC addresses, enables devices to connect to the Internet and interact locally with each other.

How Does TCP Compare to QUIC?

TCP/IP remains the most common way for devices to connect to the Internet. Like TCP, QUIC is a transport protocol, but it approaches data transmission differently.

First, QUIC is built on UDP, not TCP. UDP prioritizes speed over reliability, which means data packets may not always arrive in order or at all.

With UDP, you can expect some packet loss and reduced efficiency in exchange for higher speed. QUIC, building on this foundation, provides mechanisms to minimize packet loss whenever possible.

TCP is more efficient at delivering packets but at lower speeds than UDP. TCP can retransmit lost packets as a backup, but this is less efficient than sending everything correctly the first time.

Compared to TCP, QUIC sends packets faster and with better reordering of lost packets. QUIC also encrypts packets by default, while TCP uses a separate protocol for encryption.

QUIC delivers UDP-level speed with TCP-like efficiency features—in other words, it combines the best of both protocols.

Will QUIC Ever Replace TCP and UDP?

Since TCP has been the most widely used data transmission protocol for many years, it will remain the default standard for some time. However, QUIC is gaining momentum, and its adoption continues to grow year after year.

It’s unlikely that QUIC will completely replace TCP or UDP, as each protocol has its own purpose and should continue to coexist in the future.

Nevertheless, QUIC could improve local network performance for desktop devices and boost the efficiency of 5G mobile networks. This would be convenient for streaming content at home or web surfing on the go.

What Does HTTP/3 Mean for the Future of QUIC?

Although HTTP/3 is the most modern and advanced standard for transmitting information on the web, most of the Internet still runs on HTTP/2 and HTTP/1.

HTTP/3 supports QUIC features by default, while HTTP/2 and HTTP/1 rely on TCP. This means the adoption rates of HTTP/3 and QUIC are directly linked, so their widespread use is likely to happen around the same time.

Which Operating Systems Already Support QUIC by Default?

In addition to industry-wide support for HTTP/3 and QUIC, similar integration is needed at the operating system level.

Proper built-in QUIC support allows devices to use the protocol’s features system-wide. The good news is that the latest versions of Windows and macOS already support QUIC by default.

For example, if you have at least Windows 10 21H1 or any version of Windows 11, your device supports QUIC. For macOS, if you have Big Sur (macOS 11) or later, your device also has the necessary support.

Linux support is still in development, but some distributions already offer external drivers that provide access to QUIC features.

We’ll likely see proper built-in QUIC support in Linux only after the protocol becomes more widely adopted in the industry.

Does Android Support the QUIC Protocol?

There is some initial support for QUIC on mobile devices. On Android, developers use Cronet to implement HTTP/3 features in their apps, which also allows them to use QUIC features individually.

Android does not support QUIC at the system level, but app developers can use it as needed. For example, Google Chrome supports QUIC because it supports HTTP/3. Websites with server-side QUIC features also work in all modern versions of Google Chrome.

Starting with Android 11, DNS-over-HTTP/3 (DoH3) is fully supported via the Private DNS feature. However, it only allows you to choose from pre-configured DNS providers like Google DNS or Cloudflare DNS. Starting with Android 13, you can specify a hostname for DoH3 instead of relying on a preset list.

Not all servers support this feature yet, but the list is growing. Private DNS with DoH3 speeds up DNS lookups on Android using HTTP/3, which by default provides certain QUIC features.

Does iOS Support the QUIC Protocol?

Apple supports QUIC and HTTP/3 starting with iOS 15. If your device runs iOS 15 or later and the app’s server supports QUIC features, your device will work with the QUIC protocol.

The Apple Safari browser appears to support HTTP/3, but you may need to enable it manually. In some system versions, it may be enabled by default, which is a good sign for QUIC’s future. So, Safari should support QUIC as long as HTTP/3 is enabled in the app’s settings.

Conclusion

Technological progress is inevitable, and new protocols will gradually replace outdated solutions. While TCP will likely remain the gold standard for years to come, QUIC will eventually take the lead. This is no surprise, as it combines the best of TCP and UDP while offering unique features.

Transitioning to new standards always comes with challenges and takes time, but ultimately, it paves the way for more efficient, secure, and high-performance communications. Being ready to adapt and adopt cutting-edge technologies is the key to success in our rapidly evolving digital world.