Content Delivery Network Interconnection (CDNI) Control Interface / Triggers 2nd Edition
draft-sopher-cdni-triggers-extensions-rfc8007bis-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ori Finkelman , Sanjay Mishra , Nir Baruch Sopher | ||
Last updated | 2021-07-08 | ||
Replaced by | draft-sopher-cdni-ci-triggers-rfc8007bis | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-sopher-cdni-ci-triggers-rfc8007bis | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document obsoletes RFC8007. This document describes the part of the Content Delivery Network Interconnection (CDNI) Control interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-position metadata or content or to request that it invalidate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN.
Authors
Ori Finkelman
Sanjay Mishra
Nir Baruch Sopher
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)