RFC 9569: The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
In plain English — editorial summary, not part of the RFC
"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.
Document record
- Document ID
- RFC9569
- Published
- September 2024
- Authors
- K. Gao; R. Schott; Y. R. Yang; L. Delwiche; L. Keller
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9567DNS Error ReportingCurrent
April 2024
- RFC 9565An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information ElementCurrent
March 2024
- RFC 9560Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID ConnectCurrent
April 2024
- RFC 9582A Profile for Route Origin Authorizations (ROAs)Current
May 2024
- RFC 9589On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed ObjectsCurrent
May 2024
- RFC 9544Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs)Current
March 2024
- RFC 9537Redacted Fields in the Registration Data Access Protocol (RDAP) ResponseCurrent
March 2024
- RFC 9536Registration Data Access Protocol (RDAP) Reverse SearchCurrent
April 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?