draft-ietf-quic-recovery
E249196
draft-ietf-quic-recovery was an Internet-Draft in the IETF QUIC working group that specified loss detection and congestion control mechanisms for the QUIC transport protocol prior to its standardization in RFC 9002.
All labels observed (2)
| Label | Occurrences |
|---|---|
| QUIC Recovery | 1 |
| draft-ietf-quic-recovery canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2260234 — 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: draft-ietf-quic-recovery Context triple: [RFC 9002, obsoletes, draft-ietf-quic-recovery]
-
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.
Multiplexed Application Substrate over QUIC Encryption
Multiplexed Application Substrate over QUIC Encryption (MASQUE) is an IETF protocol framework that enables tunneling and multiplexing of multiple network flows, such as HTTP and VPN-like traffic, over a single QUIC connection to improve privacy and performance.
-
C.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
D.
DNS over QUIC (DoQ)
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.
-
E.
HTTP/3 QPACK header compression specification
The HTTP/3 QPACK header compression specification defines the mechanism for efficiently compressing HTTP header fields over QUIC while avoiding head-of-line blocking.
- 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: draft-ietf-quic-recovery Target entity description: draft-ietf-quic-recovery was an Internet-Draft in the IETF QUIC working group that specified loss detection and congestion control mechanisms for the QUIC transport protocol prior to its standardization in RFC 9002.
-
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.
Multiplexed Application Substrate over QUIC Encryption
Multiplexed Application Substrate over QUIC Encryption (MASQUE) is an IETF protocol framework that enables tunneling and multiplexing of multiple network flows, such as HTTP and VPN-like traffic, over a single QUIC connection to improve privacy and performance.
-
C.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
D.
DNS over QUIC (DoQ)
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.
-
E.
HTTP/3 QPACK header compression specification
The HTTP/3 QPACK header compression specification defines the mechanism for efficiently compressing HTTP header fields over QUIC while avoiding head-of-line blocking.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF document
ⓘ
Internet-Draft ⓘ QUIC working group document ⓘ |
| appliesTo |
QUIC endpoints
ⓘ
QUIC receivers ⓘ QUIC senders ⓘ |
| area |
IETF Areas
ⓘ
surface form:
IETF Transport Area
|
| category | transport protocol specification ⓘ |
| defines |
ECN handling for QUIC
ⓘ
QUIC congestion control algorithms ⓘ QUIC loss detection algorithms ⓘ RTO and PTO computation for QUIC ⓘ ack-based loss detection for QUIC ⓘ acknowledgment handling for QUIC ⓘ congestion avoidance behavior for QUIC ⓘ congestion window management for QUIC ⓘ initial congestion control parameters for QUIC ⓘ pacing recommendations for QUIC ⓘ packet loss detection for QUIC ⓘ receiver-side considerations for QUIC recovery ⓘ recovery from packet loss for QUIC ⓘ retransmission strategies for QUIC ⓘ sender-side recovery behavior for QUIC ⓘ slow start behavior for QUIC ⓘ spurious loss detection handling for QUIC ⓘ timer-based loss detection for QUIC ⓘ |
| focus |
congestion control
ⓘ
loss detection ⓘ recovery mechanisms for QUIC ⓘ |
| intendedStatus | Proposed Standard ⓘ |
| obsoletedBy | RFC 9002 ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| relatedProtocol | QUIC ⓘ |
| relation | part of QUIC transport standardization effort ⓘ |
| relationship |
companion to draft-ietf-quic-tls
ⓘ
companion to draft-ietf-quic-transport ⓘ |
| scope | Internet transport protocols ⓘ |
| standardizationStage | pre-RFC ⓘ |
| status | superseded ⓘ |
| successor | RFC 9002 ⓘ |
| title | QUIC Loss Detection and Congestion Control ⓘ |
| topic |
congestion control research
ⓘ
loss recovery in encrypted transports ⓘ transport-layer performance ⓘ |
| usedBy | QUIC implementers during development prior to RFC 9002 ⓘ |
| workGroup | IETF 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: draft-ietf-quic-recovery Description of subject: draft-ietf-quic-recovery was an Internet-Draft in the IETF QUIC working group that specified loss detection and congestion control mechanisms for the QUIC transport protocol prior to its standardization in RFC 9002.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.