Lesson plan
QUIC
QUIC ( ) is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google. It was first implemented and deployed in 2012 and was publicly announced in 2013 as experimentation broadened. It was also described at an IETF meeting. QUIC is supported by major web browsers, including Chrome, Edge, Firefox, and Safari. In Chrome, QUIC is used by more than half of all connections to Google's servers. QUIC improves performance of connection-oriented web applications that previously relied on Transmission Control Protocol (TCP). It does this by establishing a number of multiplexed connections between two endpoints using User Datagram Protocol (UDP), and it is designed to obsolete TCP at the transport layer for many applications. Although its name was initially proposed as an acronym for Quick UDP Internet Connections, in IETF's use of the word QUIC is not an acronym; it is simply the name of the protocol. 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, which is carried over TCP, can suffer head-of-line-blocking delays if multiple streams are multiplexed on a TCP connection and any of the TCP packets on that connection are delayed or lost.…
Article summary
QUIC ( ) is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google. It was first implemented and deployed in 2012 and was publicly announced in 2013 as experimentation broadened. It was also described at an IETF meeting. QUIC is supported by major web browsers, including Chrome, Edge, Firefox, and Safari. In Chrome, QUIC is used by more than half of all connections to Google's servers. QUIC improves performance of connection-oriented web applications that previously relied on Transmission Control Protocol (TCP). It does this by establishing a number of multiplexed connections between two endpoints using User Datagram Protocol (UDP), and it is designed to obsolete TCP at the transport layer for many applications. Although its name was initially proposed as an acronym for Quick UDP Internet Connections, in IETF's use of the word QUIC is not an acronym; it is simply the name of the protocol. 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, which is carried over TCP, can suffer head-of-line-blocking delays if multiple streams are multiplexed on a TCP connection and any of the TCP packets on that connection are delayed or lost.…
Key claims
- date of establishment: 2016 — source: Wikipedia, revision 1374045936, retrieved 2026-10-20 · confidence 0.95
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- The record states that the date of establishment is "2016". What evidence would count against this claim?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
- Wikipedia, “QUIC”, revision 1374045936, retrieved 2026-10-20 https://en.wikipedia.org/w/index.php?oldid=1374045936
Key claims and bibliography are generated from the same tracked claims and sources as the article page.