HTTP Datagrams
E835148
HTTP Datagrams are a mechanism for sending unreliable, connection-associated data alongside HTTP requests and responses, enabling low-latency, datagram-style communication over HTTP.
All labels observed (2)
| Label | Occurrences |
|---|---|
| HTTP CONNECT method | 1 |
| HTTP Datagrams canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10024737 — 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: HTTP Datagrams Context triple: [IETF MASQUE Working Group, standardizes, HTTP Datagrams]
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
RPC over HTTP
RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
-
C.
Datagram Delivery Protocol
Datagram Delivery Protocol is the connectionless network-layer protocol of the AppleTalk suite, responsible for routing and delivering datagram packets between AppleTalk nodes.
-
D.
UDP
UDP (User Datagram Protocol) is a lightweight, connectionless transport-layer protocol used on the Internet for fast, low-overhead data transmission without guaranteed delivery or ordering.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- 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: HTTP Datagrams Target entity description: HTTP Datagrams are a mechanism for sending unreliable, connection-associated data alongside HTTP requests and responses, enabling low-latency, datagram-style communication over HTTP.
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
RPC over HTTP
RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
-
C.
Datagram Delivery Protocol
Datagram Delivery Protocol is the connectionless network-layer protocol of the AppleTalk suite, responsible for routing and delivering datagram packets between AppleTalk nodes.
-
D.
UDP
UDP (User Datagram Protocol) is a lightweight, connectionless transport-layer protocol used on the Internet for fast, low-overhead data transmission without guaranteed delivery or ordering.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP extension mechanism
ⓘ
datagram-based transport feature ⓘ networking mechanism ⓘ |
| associatedWith |
HTTP requests
ⓘ
HTTP responses ⓘ |
| benefit |
avoids head-of-line blocking for datagram-style traffic
ⓘ
reduced latency compared to stream-based delivery for some use cases ⓘ |
| canBeMappedTo | underlying transport datagrams ⓘ |
| canBeSecuredBy |
QUIC-TLS over HTTP/3
ⓘ
TLS over HTTP/2 or HTTP/1.1 ⓘ |
| canBeUsedFor |
gaming traffic over HTTP
ⓘ
media or live data over HTTP ⓘ real-time communication over HTTP ⓘ telemetry over HTTP ⓘ |
| coexistsWith | traditional HTTP message-based communication ⓘ |
| contrastsWith |
reliable HTTP message bodies
ⓘ
stream-oriented HTTP data ⓘ |
| designedFor |
applications that can tolerate packet loss
ⓘ
low-latency applications ⓘ |
| doesNotReplace | standard HTTP request-response semantics ⓘ |
| enables |
datagram-style communication over HTTP
ⓘ
low-latency communication over HTTP ⓘ unreliable data transmission over HTTP ⓘ |
| goal |
allow applications to use a single HTTP connection for both reliable and unreliable data
ⓘ
support datagram semantics within the HTTP ecosystem ⓘ |
| hasProperty |
can be associated with specific HTTP requests or responses
ⓘ
can be multiplexed with regular HTTP traffic ⓘ can carry application-defined payloads ⓘ does not guarantee delivery ⓘ does not guarantee duplication avoidance ⓘ does not guarantee ordering ⓘ shares congestion control with HTTP connection ⓘ shares security context with HTTP connection ⓘ |
| isPartOf | the broader effort to extend HTTP for real-time applications ⓘ |
| provides | unreliable, connection-associated data channel ⓘ |
| relatedTo |
HTTP/3 datagram extensions
ⓘ
linked to:
HTTP/3
QUIC DATAGRAM frames ⓘ |
| requires |
HTTP extension negotiation
ⓘ
support from both client and server ⓘ |
| scope | data sent alongside HTTP requests and responses ⓘ |
| securityInheritedFrom | the underlying HTTP connection ⓘ |
| transportedOver |
HTTP connections
ⓘ
HTTP/3 connections ⓘ |
| usedBy | applications needing unreliable, low-latency channels over HTTP ⓘ |
| uses | connection-associated context ⓘ |
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: HTTP Datagrams Description of subject: HTTP Datagrams are a mechanism for sending unreliable, connection-associated data alongside HTTP requests and responses, enabling low-latency, datagram-style communication over HTTP.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: HTTP Datagrams