datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Content Distribution Network Interconnection (CDNI) Metadata Interface
draft-ma-cdni-metadata-03

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-01-17 (latest revision 2012-07-16)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-ma-cdni-metadata-03.txt

Abstract

Content publishers (CPs) often use multiple Content Delivery Networks (CDNs) to deliver content to consumers. Though existing interactions between CPs and individual CDNs are beyond the scope of CDN interconnection (CDNI), it is important to understand the management capabilities and features available with existing non-interconnected multi-CDN deployments. Before migrating to CDNI, CPs must first assess the suitability of CDNI as a replacement for their existing non-interconnected multi-CDN deployments. CDN feature configuration and capability advertisement and enforcement is likely to occur through the CDNI metadata interface (MI). This document describes an approach to implementing the CDNI MI through the use of an extensible metadata model and a light-weight HTTP-based API.

Authors

Kevin Ma <kevin.ma@azukisystems.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)