DNS over QUIC (DoQ)
E40276
DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
All labels observed (3)
| Label | Occurrences |
|---|---|
| DNS over QUIC | 3 |
| DNS over Dedicated QUIC Connections | 1 |
| DNS over QUIC (DoQ) canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T311026 — 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: DNS over QUIC (DoQ) Context triple: [QUIC, transportFor, DNS over QUIC (DoQ)]
-
A.
QUIC
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.
-
B.
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.
-
C.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
-
D.
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.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: DNS over QUIC (DoQ) Target entity description: DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
-
A.
QUIC
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.
-
B.
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.
-
C.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
-
D.
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.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
DNS transport protocol
ⓘ
encrypted transport protocol ⓘ network protocol ⓘ |
| abbreviation | DoQ ⓘ |
| avoids |
TCP head-of-line blocking
ⓘ
cleartext DNS on the wire ⓘ |
| canBeUsedBy |
authoritative DNS servers
ⓘ
recursive resolvers ⓘ stub resolvers ⓘ |
| connectionEstablishment | client-initiated QUIC connection to DNS server ⓘ |
| defaultPort | 853 ⓘ |
| definedInRFC | RFC 9250 ⓘ |
| designGoal | minimal changes to DNS message format ⓘ |
| feature |
0-RTT resumption
ⓘ
connection-oriented communication ⓘ encryption ⓘ forward secrecy ⓘ head-of-line blocking avoidance ⓘ improved reliability ⓘ integrity protection ⓘ multiplexing ⓘ privacy protection against passive observers ⓘ reduced latency ⓘ |
| goal |
improve DNS performance
ⓘ
improve DNS privacy ⓘ improve DNS reliability ⓘ |
| improvesOver |
DNS over DTLS
ⓘ
DNS over TCP ⓘ DNS over UDP ⓘ |
| layer | application layer ⓘ |
| messageFormat | standard DNS wire format in QUIC streams ⓘ |
| providesFunction | transport for DNS messages ⓘ |
| publicationYear | 2022 ⓘ |
| relatedTo |
DTLS
ⓘ
surface form:
DNS over DTLS
DNS over HTTPS ⓘ DNS over TLS ⓘ |
| runsOver | QUIC connections on UDP port 853 ⓘ |
| securityModelSimilarTo | DNS over TLS ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | Proposed Standard ⓘ |
| supports |
DNS queries
ⓘ
DNS responses ⓘ connection reuse for multiple DNS queries ⓘ multiple DNS streams over a single QUIC connection ⓘ server push is not used for DNS data ⓘ |
| uses | TLS 1.3 handshake within QUIC ⓘ |
| usesTransportProtocol | QUIC ⓘ |
| usesUnderlyingProtocol | UDP ⓘ |
| workingGroup |
IETF DNSOP
ⓘ
IETF QUIC Working Group ⓘ
surface form:
IETF QUIC
|
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: DNS over QUIC (DoQ) Description of subject: DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.