QUIC
E7606
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
All labels observed (8)
| Label | Occurrences |
|---|---|
| QUIC canonical | 29 |
| QUIC transport protocol | 7 |
| QUIC: A UDP-Based Multiplexed and Secure Transport | 2 |
| Google QUIC | 1 |
| QUIC Transport | 1 |
| QUIC path validation | 1 |
| QUIC protocol suite | 1 |
| inherits security properties of QUIC | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T63733 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: QUIC Context triple: [UDP, usedBy, QUIC]
-
A.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
D.
ChaCha20
ChaCha20 is a modern stream cipher designed by Daniel J. Bernstein, widely used for its high performance and strong security in protocols like TLS.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: QUIC Target entity description: QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
A.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
D.
ChaCha20
ChaCha20 is a modern stream cipher designed by Daniel J. Bernstein, widely used for its high performance and strong security in protocols like TLS.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Internet protocol ⓘ multiplexed transport protocol ⓘ transport protocol ⓘ |
| aimsTo |
improve reliability
ⓘ
improve security ⓘ improve web performance ⓘ reduce latency ⓘ |
| avoids | head-of-line blocking at transport layer ⓘ |
| definedIn |
RFC 9000
ⓘ
RFC 9001 ⓘ RFC 9002 ⓘ |
| designedFor |
HTTP
ⓘ
web traffic ⓘ |
| developedBy | Google ⓘ |
| enables |
connection migration across IP addresses
ⓘ
faster connection setup than TCP+TLS ⓘ multiplexed streams over a single connection ⓘ |
| IANAProtocolNumber | UDP-based; no separate IP protocol number ⓘ |
| initialDeploymentBy |
Google Chrome
ⓘ
Google ⓘ
surface form:
Google servers
|
| initialDevelopmentYear | 2012 ⓘ |
| layer | transport layer ⓘ |
| obsoletes | Google QUIC (gQUIC) drafts ⓘ |
| provides |
authentication
ⓘ
encryption ⓘ integrity protection ⓘ |
| publicationYear | 2021 ⓘ |
| relatedTo |
HTTP/2
ⓘ
Transmission Control Protocol ⓘ
surface form:
TCP
TLS ⓘ |
| runsOver | UDP ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| supports |
0-RTT connection establishment
ⓘ
RFC 8446 ⓘ
surface form:
TLS 1.3
congestion control ⓘ connection migration ⓘ loss recovery ⓘ multiplexing ⓘ stream multiplexing ⓘ |
| transportFor |
DNS over QUIC (DoQ)
ⓘ
MASQUE ⓘ |
| underlies | HTTP/3 ⓘ |
| usedBy | HTTP/3 ⓘ |
| uses |
connection identifiers
ⓘ
encrypted transport headers ⓘ packet numbers ⓘ user space congestion control ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: QUIC Description of subject: QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
Referenced by (43)
Full triples — surface form annotated when it differs from this entity's canonical label.