QUIC (/kwɪk/) is a general-purpose[1] transport layer[2] network protocol initially designed by Jim Roskind at Google,[3] implemented, and deployed in 2012,[4] announced publicly in 2013 as experimentation broadened,[5][6][7] and described at an IETF meeting.[8] QUIC is used by more than half of all connections from the Chrome web browser to Google's servers.[9] Microsoft Edge (which, after version 1, is a derivative of the open-source Chromium browser),[10][11] Firefox,[12] and Safari support it.[13]
Although its name was initially proposed as the acronym for "Quick UDP Internet Connections",[3][8] IETF's use of the word QUIC is not an acronym; it is simply the name of the protocol.[1] QUIC improves performance of connection-oriented web applications that are currently using TCP.[2][9] It does this by establishing a number of multiplexed connections between two endpoints using User Datagram Protocol (UDP), and is designed to obsolete TCP at the transport layer for many applications, thus earning the protocol the occasional nickname "TCP/2".[14]
QUIC works hand-in-hand with HTTP/3's multiplexed connections, allowing multiple streams of data to reach all the endpoints independently, and hence independent of packet losses involving other streams. In contrast, HTTP/2 hosted on Transmission Control Protocol (TCP) can suffer head-of-line-blocking delays of all multiplexed streams if any of the TCP packets are delayed or lost.
QUIC's secondary goals include reduced connection and transport latency, and bandwidth estimation in each direction to avoid congestion. It also moves congestion control algorithms into the user space at both endpoints, rather than the kernel space, which it is claimed will allow these algorithms to improve more rapidly. Additionally, the protocol can be extended with forward error correction (FEC) to further improve performance when errors are expected, and this is seen as the next step in the protocol's evolution. It has been designed to avoid protocol ossification so that it remains evolvable, unlike TCP, which has suffered significant ossification.
In June 2015, an Internet Draft of a specification for QUIC was submitted to the IETF for standardization.[15][16] A QUIC working group was established in 2016.[17] In October 2018, the IETF's HTTP and QUIC Working Groups jointly decided to call the HTTP mapping over QUIC "HTTP/3" in advance of making it a worldwide standard.[18] In May 2021, the IETF standardized QUIC in RFC 9000, supported by RFC 8999, RFC 9001 and RFC 9002.[19] DNS-over-QUIC is another application.
^ abCite error: The named reference rfc9000 was invoked but never defined (see the help page).
^ abCite error: The named reference LWN was invoked but never defined (see the help page).
^ abCite error: The named reference QUIC Design Doc was invoked but never defined (see the help page).
^Cite error: The named reference Chromium Code Merging QUIC was invoked but never defined (see the help page).
^Cite error: The named reference chromium_announcement was invoked but never defined (see the help page).
^Cite error: The named reference Google Working on QUIC was invoked but never defined (see the help page).
^Cite error: The named reference quic_youtube was invoked but never defined (see the help page).
^ abCite error: The named reference IETF QUIC Intro was invoked but never defined (see the help page).
^ abLardinois, Frederic (18 April 2015). "Google Wants To Speed Up The Web With Its QUIC Protocol". TechCrunch. Retrieved 2016-10-25.
^Mackie, Kurt; August 26, 2021. "Microsoft Embracing Native QUIC in Newer Windows OSes and Edge Browser". Redmond Magazine. Retrieved 2022-05-08.{{cite web}}: CS1 maint: numeric names: authors list (link)
^Christopher Fernandes (April 3, 2018). "Microsoft to add support for Google's QUIC fast internet protocol in Windows 10 Redstone 5". Retrieved 2020-05-08.
^Dragana Damjanovic (2021-04-16). "QUIC and HTTP/3 Support now in Firefox Nightly and Beta". Mozilla. Retrieved 2021-10-11.
^Cite error: The named reference safari16 was invoked but never defined (see the help page).
^Cite error: The named reference Call it TCP/2. One More Time. was invoked but never defined (see the help page).
^"Google Will Propose QUIC As IETF Standard". InfoQ. Retrieved 2016-10-25.
^"I-D Action: draft-tsvwg-quic-protocol-00.txt". i-d-announce (Mailing list). 17 Jun 2015.
^"QUIC - IETF Working Group". datatracker.ietf.org. Retrieved 2016-10-25.
^Cimpanu, Catalin (12 November 2018). "HTTP-over-QUIC to be renamed HTTP/3". ZDNet.
^"QUIC is now RFC 9000". www.fastly.com. 2021-05-27. Retrieved 2021-05-28.
QUIC (/kwɪk/) is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google, implemented, and deployed in 2012, announced...
MsQuic is a free and open source implementation of the IETF QUIC protocol written in C that is officially supported on the Microsoft Windows (including...
lossless, bi-directional connections—typically, TCP/IP, but also possibly over QUIC. It is an open OASIS standard and an ISO recommendation (ISO/IEC 20922)....
published in 2022 by the Internet Engineering Task Force, describes DNS over QUIC. It has "privacy properties similar to DNS over TLS (DoT) [...], and latency...
reliable connections. QUIC is a transport protocol built on top of UDP. QUIC provides a reliable and secure connection. HTTP/3 uses QUIC as opposed to earlier...
browsers, i.e. (at least partially) supported by 97% of users. HTTP/3 uses QUIC instead of TCP for the underlying transport protocol. Like HTTP/2, it does...
HTTP/2-enabled websites. As of April 2020, LSWS was used by 69.3% of websites using QUIC and 47.6% of websites using HTTP/3. According to a Netcraft web server survey...
decided to fork the project as QuicTLS and support these patches on top of the OpenSSL code in order to unblock QUIC development. This action was generally...
transport services such as DNS over TLS (DoT), DNS over HTTPS (DoH) and DNS over QUIC (DoQ). Public DNS resolvers are operated either by commercial companies,...
(2010-10-30). "Multipath Extension for QUIC". IETF. Q. De Coninck; O. Bonaventure (2010-12-12). "Multipath QUIC: Design and Evaluation" (PDF). Proc. Conext'2017...
also allows the use of HTTP/2 and HTTP/3 (and their predecessors SPDY and QUIC), which are new HTTP versions designed to reduce page load times, size, and...
supported by most modern browsers. In HTTP/3, multiplexing is accomplished via QUIC which replaces TCP. This further reduces loading time, as there is no head-of-line...
Jim Roskind is an American software engineer best known for designing the QUIC protocol in 2012 while being an employee at Google. Roskind co-founded Infoseek...
Divyashri; Rizk, Amr; Zink, Michael (June 2017). "Not so QUIC: A Performance Study of DASH over QUIC". NOSSDAV'17: Proceedings of the 27th Workshop on Network...
brain autopsy post-mortem. The real-time quaking-induced conversion (RT-QuIC), a highly sensitive assay that detects minute amounts of PrPSc in the cerebrospinal...
existing ossification requires coordination across protocol participants. QUIC is the first IETF transport protocol to have been designed with deliberate...
via the DMA path DNS over HTTPS AES-256 encryption of SMB traffic SMB over QUIC instead of TCP Storage Migration Service (SMS) Compression of SMB traffic...
technologies, including DNSCrypt, DNS over HTTPS, DNS over TLS, and DNS over QUIC. AdGuard began testing DNS service back in 2016, and officially launched...
He is active in the IETF, a member of the working groups for HTTP/2 and QUIC, and contributed to several RFCs. In April 2023, he became a member of the...
(e.g., due to outer checksums made redundant by inner integrity checks). QUIC takes the latter approach, rebuilding reliable stream transport on top of...
Global Information