RFC 9114
E8958
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9114 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T53993 — 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 9114 Context triple: [HTTP, definedIn, RFC 9114]
-
A.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
E.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
- 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 9114 Target entity description: RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
A.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
E.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP specification
ⓘ
Internet standard ⓘ Request for Comments ⓘ |
| area | Applications and Real-Time Area ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP/3 connection establishment over QUIC
ⓘ
HTTP/3 connection management ⓘ HTTP/3 error codes ⓘ HTTP/3 frame types ⓘ HTTP/3 header compression usage ⓘ HTTP/3 prioritization model ⓘ HTTP/3 request and response exchange ⓘ HTTP/3 server push behavior ⓘ HTTP/3 ⓘ
surface form:
HTTP/3 stream types
mapping of HTTP semantics to QUIC ⓘ semantics of HTTP/3 over QUIC ⓘ |
| focusesOn |
multiplexed streams over QUIC
ⓘ
performance improvements over HTTP/2 ⓘ reduced head-of-line blocking ⓘ |
| format |
HTML
ⓘ
PDF ⓘ Text ⓘ |
| fullTitle | HTTP/3 ⓘ |
| language | English ⓘ |
| obsoletes |
HTTP/2
ⓘ
HTTP/2 ⓘ
surface form:
RFC 7540
|
| partOf | HTTP family ⓘ |
| protocolNumber | 9114 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| references |
HTTP Caching
ⓘ
RFC 7231 ⓘ
surface form:
HTTP Semantics
HTTP/1.1 ⓘ QUIC ⓘ
surface form:
QUIC: A UDP-Based Multiplexed and Secure Transport
RFC 9000 ⓘ RFC 9110 ⓘ RFC 9111 ⓘ RFC 9112 ⓘ |
| specifiesProtocol | HTTP/3 ⓘ |
| specifiesVersionOf |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| standardizes | use of QUIC for HTTP ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | HTTP/3 ⓘ |
| updates | HTTP architecture ⓘ |
| usesTransportProtocol | QUIC ⓘ |
| workingGroup |
HTTP Working Group
ⓘ
HTTP Working Group ⓘ
surface form:
IETF HTTPbis 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 9114 Description of subject: RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.