RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) Protocol that generalizes the concept of "endpoint properties", which have been tied to IP addresses so far, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO Protocol. While supporting the endpoints and related Endpoint Property Service defined in RFC 7285, the ALTO Protocol is extended in two major directions. First, from endpoints restricted to IP addresses to entities covering a wider and extensible set of objects; second, from properties for specific endpoints to entire entity property maps. These extensions introduce additional features that allow entities and property values to be specific to a given information resource. This is made possible by a generic and flexible design of entity and property types.
Document record
- Document ID
- RFC9240
- Published
- July 2022
- Authors
- W. Roome; S. Randriamasy; Y. Yang; J. Zhang; K. Gao
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 53
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9241Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)Current
July 2022
- RFC 8895Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)Current
November 2020
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 9232Network Telemetry FrameworkCurrent
May 2022
- RFC 9255The 'I' in RPKI Does Not Stand for IdentityCurrent
June 2022
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 9222Guidelines for Autonomic Service AgentsCurrent
March 2022
- RFC 9210DNS Transport over TCP - Operational RequirementsCurrent
March 2022
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?