RFC 9000
E48577
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9000 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T311017 — 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 9000 Context triple: [QUIC, definedIn, RFC 9000]
-
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 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
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.
- 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 9000 Target entity description: 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.
-
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 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
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.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF RFC
ⓘ
Internet standard ⓘ technical specification ⓘ |
| aimsTo |
enable efficient multiplexing without head-of-line blocking
ⓘ
improve robustness to network changes ⓘ reduce latency compared to TCP ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| defines |
QUIC congestion control hooks
ⓘ
QUIC connection IDs ⓘ QUIC connection establishment ⓘ QUIC connection migration mechanisms ⓘ QUIC error codes ⓘ QUIC flow control ⓘ QUIC handshake behavior in transport layer ⓘ QUIC loss detection framework ⓘ QUIC packet number spaces ⓘ QUIC packetization ⓘ QUIC ⓘ
surface form:
QUIC path validation
QUIC stream multiplexing ⓘ QUIC transport parameters ⓘ QUIC ⓘ
surface form:
QUIC transport protocol
QUIC version negotiation ⓘ |
| excludes |
HTTP/3 semantics
ⓘ
application protocols over QUIC ⓘ |
| focusesOn | transport layer aspects of QUIC ⓘ |
| intendedUse | general-purpose Internet transport ⓘ |
| obsoletes |
QUIC TLS usage specification
ⓘ
surface form:
draft-ietf-quic-transport
|
| partOf | QUIC RFC suite ⓘ |
| protocolFamily | QUIC ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 8999
ⓘ
RFC 9001 ⓘ RFC 9002 ⓘ |
| securityModel | relies on QUIC-TLS defined in RFC 9001 ⓘ |
| specifies |
core QUIC transport mechanisms
ⓘ
low-latency communication over UDP ⓘ multiplexed transport over UDP ⓘ secure transport over UDP ⓘ |
| status | Internet Standard ⓘ |
| stream | IETF Stream ⓘ |
| supports |
0-RTT connection establishment (via QUIC-TLS)
ⓘ
connection migration for mobile clients ⓘ encrypted transport headers (except limited invariants) ⓘ stream-level flow control ⓘ |
| title |
QUIC
ⓘ
surface form:
QUIC: A UDP-Based Multiplexed and Secure Transport
|
| usesUnderlyingProtocol | UDP ⓘ |
| workingGroup |
IETF QUIC Working Group
ⓘ
surface form:
QUIC Working Group
|
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 9000 Description of subject: 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.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.