The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
RFC 9569
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['incremental update']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "L. Keller": changed name from "Lachlan Keller" to "L. Keller", cleared country (was "USA") |
|
2026-05-20
|
(System) | Changed author "L. Delwiche": changed name from "Lauren Delwiche" to "L. Delwiche", cleared country (was "USA") |
|
2026-05-20
|
(System) | Changed author "Y. R. Yang": changed name from "Y. Richard Yang" to "Y. R. Yang", cleared country (was "USA") |
|
2026-05-20
|
(System) | Changed author "R. Schott": changed name from "Roland Schott" to "R. Schott", cleared country (was "Germany") |
|
2026-05-20
|
(System) | Changed author "K. Gao": changed name from "Kai Gao" to "K. Gao", cleared country (was "China") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-09-10
|
(System) | Received changes through RFC Editor sync (created document RFC 9569, created became rfc relationship between draft-ietf-alto-new-transport and RFC 9569, set title to 'The … Received changes through RFC Editor sync (created document RFC 9569, created became rfc relationship between draft-ietf-alto-new-transport and RFC 9569, set title to 'The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)', set abstract to '"Application-Layer Traffic Optimization (ALTO) Protocol" (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource, one at a time. RFC 8895, which describes ALTO incremental updates using Server-Sent Events (SSE), defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly and concurrently (in a non-blocking manner) request (or pull) specific incremental updates using HTTP/2 or HTTP/3, while still functioning for HTTP/1.1.', set pages to 40, set standardization level to Proposed Standard, added RFC published event at 2024-09-10) |
|
2024-09-10
|
(System) | RFC published |