RFC 9241: Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
In plain English — editorial summary, not part of the RFC
The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008.
Document record
- Document ID
- RFC9241
- Published
- July 2022
- Authors
- J. Seedorf; Y. Yang; K. Ma; J. Peterson; J. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 42
- 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 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?