Content Delivery Networks Interconnection (cdni)
| WG | Name | Content Delivery Networks Interconnection | |
|---|---|---|---|
| Acronym | cdni | ||
| Area | Web and Internet Transport (wit) | ||
| State | Active | ||
| Charter | charter-ietf-cdni-03 Approved | ||
| Document dependencies | |||
| Additional resources | Issue tracker, Wiki, Zulip Stream | ||
| Personnel | Chairs | Chris Lemmons, Kevin J. Ma, Sanjay Mishra | |
| Area Director | Gorry Fairhurst | ||
| Mailing list | Address | cdni@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/cdni | ||
| Archive | https://mailarchive.ietf.org/arch/browse/cdni/ | ||
| Chat | Room address | https://zulip.ietf.org/#narrow/stream/cdni |
Charter for Working Group
A Content Delivery Network (CDN) is an infrastructure of network elements operating at layer 4 through layer 7, arranged for the efficient distribution and delivery of digital content. Such content includes, but is not limited to, web pages and images delivered via HTTP, and streaming of continuous media delivered via HTTP, RTSP, RTMP, etc. CDNs typically provide services to multiple Content Service Providers (CSPs). The goal of the CDNI Working Group is to allow the interconnection of separately administered CDNs in support of the end-to-end delivery of content from CSPs through multiple CDNs and ultimately to end users (via their respective User Agents).
This Working Group is charged with maintaining and developing the specifications for CDNI. The current work items are:
Defining CDNI Metadata
The CDNI Specifications define metadata for exchanging information required for CDNs to cooperate as described in RFC 7336, Framework for Content Distribution Network Interconnection. This includes metadata definitions, defined across multiple documents, for the following:
* CDNI Request Routing interface, including the Footprint and Capabilities interface and Redirection interface;
* CDNI Metadata interface;
* CDNI Logging interface; and
* CDNI Control interface.
These interfaces define how CDNs communicate the information required to direct requests and deliver content, including all the information required to obtain, transform, synthesize, distribute, protect, and communicate about that content, as is typical for CDNs.
The working group will only define specifications that require direct communication or interoperation between CDNs. It will not define:
* New session, transport or network protocols;
* New protocols for delivering content from a CDN to an End User/User Agent;
* New protocols for ingestion of content or metadata between a CSP and a CDN;
* New protocols for acquiring content across CDNs;
* Protocols and algorithms for intra-CDN operations;
* Support for Transparent Caching across CDNs;
* New applications consuming CDNI logs; or
* Digital Right Management (DRM) mechanisms.
The working group will collaborate with other groups both inside and outside the IETF as necessary to accomplish these goals.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Dec 2026 | Recharter or dissolve | |
| Nov 2026 | Submit specification of CDNI Named Footprints to IESG as Proposed Standard |
draft-ietf-cdni-named-footprints
|
| Aug 2026 | Submit specification of CDNI Logging extensions to IESG as Proposed Standard |
draft-ietf-cdni-logging-extensions
|
| Jun 2026 | Submit specification of CDNI Client Access Control Metadata to IESG as Proposed Standard |
draft-ietf-cdni-client-access-control-metadata
|
| Mar 2026 | Submit specification of CDNI Protected Secrets Metadata to IESG as Proposed Standard |
draft-ietf-cdni-protected-secrets-metadata
|
| Mar 2026 | Submit specification of CDNI Cache Control Metadata to IESG as Proposed Standard |
draft-ietf-cdni-cache-control-metadata
|
| Dec 2025 | Submit specification of CDNI Control Triggers Interface Extensions to IESG as Proposed Standard |
draft-ietf-cdni-ci-triggers-rfc8007bis
|
| Dec 2025 | Submit specification of CDNI Edge Control Metadata to IESG as Proposed Standard |
draft-ietf-cdni-edge-control-metadata
|