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.
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
NERFINISHED
ⓘ
QUIC DATAGRAM frames NERFINISHED ⓘ |
| 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 ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.