RFC 9002
E50020
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9002 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T311019 — 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 9002 Context triple: [QUIC, definedIn, RFC 9002]
-
A.
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.
-
B.
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.
-
C.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
D.
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.
-
E.
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.
- 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 9002 Target entity description: RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
A.
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.
-
B.
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.
-
C.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ |
| appliesTo |
QUIC
ⓘ
surface form:
QUIC transport protocol
|
| area | Transport ⓘ |
| basedOn |
TCP congestion control principles
ⓘ
Transmission Control Protocol ⓘ
surface form:
TCP loss detection principles
|
| category | Standards Track ⓘ |
| defines |
ACK handling for QUIC
ⓘ
ECN response for QUIC congestion control ⓘ QUIC congestion avoidance behavior ⓘ QUIC congestion controller based on TCP NewReno ⓘ QUIC initial congestion window ⓘ QUIC loss detection timers ⓘ QUIC packet threshold loss detection ⓘ QUIC persistent congestion detection ⓘ QUIC probe timeout (PTO) mechanism ⓘ QUIC slow start behavior ⓘ QUIC time threshold loss detection ⓘ sender-side algorithms for QUIC congestion control ⓘ sender-side algorithms for QUIC loss recovery ⓘ |
| focusesOnLayer | transport layer ⓘ |
| format |
HTML
ⓘ
PDF ⓘ text ⓘ |
| intendedFor |
implementers of QUIC
ⓘ
transport protocol researchers ⓘ |
| language | English ⓘ |
| obsoletes | draft-ietf-quic-recovery ⓘ |
| partOf | QUIC specification suite ⓘ |
| protocolFamily | QUIC ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
RFC 8999
ⓘ
RFC 9000 ⓘ RFC 9001 ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| specifies |
congestion control mechanisms for QUIC
ⓘ
loss detection mechanisms for QUIC ⓘ |
| standardizes | QUIC recovery behavior across implementations ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | QUIC Loss Detection and Congestion Control ⓘ |
| uses |
ACK ranges in QUIC
ⓘ
packet number spaces in QUIC ⓘ |
| 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 9002 Description of subject: RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.