Framework for Content Distribution Network Interconnection (CDNI)
RFC 7336
| Document | Type |
RFC - Informational
(August 2014; No errata)
Obsoletes RFC 3466
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-davie-cdni-framework | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Daryl Malas | ||
| Shepherd write-up | Show (last changed 2014-01-30) | ||
| IESG | IESG state | RFC 7336 (Informational) | |
| 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 IC | ||
Internet Engineering Task Force (IETF) L. Peterson
Request for Comments: 7336 Akamai Technologies, Inc.
Obsoletes: 3466 B. Davie
Category: Informational VMware, Inc.
ISSN: 2070-1721 R. van Brandenburg, Ed.
TNO
August 2014
Framework for Content Distribution Network Interconnection (CDNI)
Abstract
This document presents a framework for Content Distribution Network
Interconnection (CDNI). The purpose of the framework is to provide
an overall picture of the problem space of CDNI and to describe the
relationships among the various components necessary to interconnect
CDNs. CDNI requires the specification of interfaces and mechanisms
to address issues such as request routing, distribution metadata
exchange, and logging information exchange across CDNs. The intent
of this document is to outline what each interface needs to
accomplish and to describe how these interfaces and mechanisms fit
together, while leaving their detailed specification to other
documents. This document, in combination with RFC 6707, obsoletes
RFC 3466.
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/rfc7336.
Peterson, et al. Informational [Page 1]
RFC 7336 CDNI Framework 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.
Peterson, et al. Informational [Page 2]
RFC 7336 CDNI Framework August 2014
Table of Contents
1. Introduction ....................................................4
1.1. Terminology ................................................4
1.2. Reference Model ............................................6
1.3. Structure of This Document ................................10
2. Building Blocks ................................................10
2.1. Request Redirection .......................................10
2.1.1. DNS Redirection ....................................10
2.1.2. HTTP Redirection ...................................12
3. Overview of CDNI Operation .....................................12
3.1. Preliminaries .............................................14
3.2. Iterative HTTP Redirect Example ...........................15
3.3. Recursive HTTP Redirection Example ........................21
3.4. Iterative DNS-Based Redirection Example ...................25
3.4.1. Notes on Using DNSSEC ..............................28
3.5. Dynamic Footprint Discovery Example .......................29
3.6. Content Removal Example ...................................31
3.7. Pre-positioned Content Acquisition Example ................32
3.8. Asynchronous CDNI Metadata Example ........................33
3.9. Synchronous CDNI Metadata Acquisition Example .............35
3.10. Content and Metadata Acquisition with Multiple
Upstream CDNs ............................................37
4. Main Interfaces ................................................38
4.1. In-Band versus Out-of-Band Interfaces .....................39
4.2. Cross-Interface Concerns ..................................40
Show full document text