RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
In plain English — editorial summary, not part of the RFC
The Application-Layer Traffic Optimization (ALTO) protocol (RFC 7285) provides network-related information, called network information resources, to client applications so that clients can make informed decisions in utilizing network resources. This document presents a mechanism to allow an ALTO server to push updates to ALTO clients to achieve two benefits: (1) updates can be incremental, in that if only a small section of an information resource changes, the ALTO server can send just the changes and (2) updates can be immediate, in that the ALTO server can send updates as soon as they are available.
Document record
- Document ID
- RFC8895
- Published
- November 2020
- Authors
- W. Roome; Y. Yang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 52
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9240An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property MapsCurrent
July 2022
- RFC 9241Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)Current
July 2022
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 8896Application-Layer Traffic Optimization (ALTO) Cost CalendarCurrent
November 2020
- RFC 8897Requirements for Resource Public Key Infrastructure (RPKI) Relying PartiesCurrent
September 2020
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 8901Multi-Signer DNSSEC ModelsCurrent
September 2020
- RFC 8889Multipoint Alternate-Marking Method for Passive and Hybrid Performance MonitoringObsoleted
August 2020
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?