RFC 9250
E204175
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9250 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1808554 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9250 Context triple: [DNS over QUIC, definedInRFC, RFC 9250]
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 9250 Target entity description: RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
DNS protocol specification
ⓘ
IETF standard ⓘ Request for Comments ⓘ |
| addresses |
DNS performance
ⓘ
DNS privacy ⓘ head-of-line blocking issues in DNS transport ⓘ |
| aimsToImprove |
performance
ⓘ
privacy ⓘ |
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines |
DNS over QUIC (DoQ)
ⓘ
surface form:
DNS over QUIC
connection management for DNS over QUIC ⓘ error handling for DNS over QUIC ⓘ message formatting for DNS over QUIC ⓘ security considerations for DNS over QUIC ⓘ use of dedicated QUIC connections for DNS ⓘ |
| documentType | Standards Track RFC ⓘ |
| enables | encrypted DNS transport over QUIC ⓘ |
| focusesOn | running DNS over QUIC ⓘ |
| goal |
enhance confidentiality of DNS traffic
ⓘ
reduce latency for DNS queries ⓘ support multiplexing of DNS queries over a single QUIC connection ⓘ |
| obsoletes | none ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| protocol | Domain Name System ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS over HTTPS
ⓘ
DNS over TLS ⓘ Domain Name System ⓘ QUIC ⓘ |
| securityModel | based on QUIC security properties ⓘ |
| series | Request for Comments ⓘ |
| specifiesProtocol |
DNS over QUIC (DoQ)
ⓘ
surface form:
DNS over QUIC
|
| standardizes | use of QUIC as a transport for DNS ⓘ |
| status | Proposed Standard ⓘ |
| title |
DNS over QUIC (DoQ)
ⓘ
surface form:
DNS over Dedicated QUIC Connections
|
| transportProtocol | QUIC ⓘ |
| updates | none ⓘ |
| useCase |
recursive to authoritative DNS transport over QUIC
ⓘ
stub to recursive DNS transport over QUIC ⓘ |
| uses | QUIC streams for DNS messages ⓘ |
| workingGroup |
IETF DNSOP
ⓘ
surface form:
DNS Operations
IETF DNSOP ⓘ
surface form:
DNSOP
|
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.
Instruction
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.
Input
Subject: RFC 9250 Description of subject: RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
DNS over QUIC