Content Distribution Network Interconnection (CDNI) Requirements
RFC 7337
| Document | Type | RFC - Informational (August 2014; No errata) | |
|---|---|---|---|
| Authors | Kent Leung , Yiu Lee | ||
| Last updated | 2018-12-20 | ||
| Replaces | draft-lefaucheur-cdni-requirements | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Daryl Malas | ||
| Shepherd write-up | Show (last changed 2013-09-19) | ||
| IESG | IESG state | RFC 7337 (Informational) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) K. Leung, Ed.
Request for Comments: 7337 Cisco
Category: Informational Y. Lee, Ed.
ISSN: 2070-1721 Comcast
August 2014
Content Distribution Network Interconnection (CDNI) Requirements
Abstract
Content delivery is frequently provided by specifically architected
and provisioned Content Delivery Networks (CDNs). As a result of
significant growth in content delivered over IP networks, existing
CDN providers are scaling up their infrastructure. Many Network
Service Providers (NSPs) and Enterprise Service Providers (ESPs) are
also deploying their own CDNs. To deliver contents from the Content
Service Provider (CSP) to end users, the contents may traverse across
multiple CDNs. This creates a need for interconnecting (previously)
standalone CDNs so that they can collectively act as a single
delivery platform from the CSP to the end users.
The goal of the present document is to outline the requirements for
the solution and interfaces to be specified by the CDNI working
group.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7337.
Leung & Lee Informational [Page 1]
RFC 7337 CDNI Requirements August 2014
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................3
2. CDNI Model and CDNI Interfaces ..................................4
3. Generic CDNI Requirements .......................................6
4. CDNI Control Interface Requirements .............................7
5. CDNI Request Routing Redirection Interface Requirements ........10
6. CDNI Footprint & Capabilities Advertisement Interface
Requirements ...................................................12
7. CDNI Metadata Interface Requirements ...........................14
8. CDNI Logging Interface Requirements ............................18
9. CDNI Security Requirements .....................................20
10. Security Considerations .......................................21
11. Contributors ..................................................21
12. Acknowledgements ..............................................21
13. References ....................................................22
13.1. Normative References .....................................22
13.2. Informative References ...................................22
1. Introduction
The volume of video and multimedia content delivered over the
Internet is rapidly increasing and expected to continue doing so in
the future. In the face of this growth, Content Delivery Networks
(CDNs) provide numerous benefits: reduced delivery cost for cacheable
content, improved quality of experience for end users, and increased
robustness of delivery. For these reasons, CDNs are frequently used
for large-scale content delivery. As a result of the significant
growth in content delivered over IP networks, existing CDN providers
are scaling up their infrastructure and many NSPs and ESPs are
deploying their own CDNs. Subject to the policy of the Content
Service Provider (CSP), it is generally desirable that a given item
Leung & Lee Informational [Page 2]
RFC 7337 CDNI Requirements August 2014
Show full document text