draft-ietf-cdni-framework-12.txt   draft-ietf-cdni-framework-13.txt 
Network Working Group L. Peterson Network Working Group L. Peterson
Internet-Draft Akamai Technologies, Inc. Internet-Draft Akamai Technologies, Inc.
Obsoletes: 3466 (if approved) B. Davie Obsoletes: 3466 (if approved) B. Davie
Intended status: Informational VMware, Inc. Intended status: Informational VMware, Inc.
Expires: November 27, 2014 R. van Brandenburg, Ed. Expires: December 1, 2014 R. van Brandenburg, Ed.
TNO TNO
May 26, 2014 May 30, 2014
Framework for CDN Interconnection Framework for CDN Interconnection
draft-ietf-cdni-framework-12 draft-ietf-cdni-framework-13
Abstract Abstract
This document presents a framework for Content Distribution Network This document presents a framework for Content Distribution Network
Interconnection (CDNI). The purpose of the framework is to provide Interconnection (CDNI). The purpose of the framework is to provide
an overall picture of the problem space of CDNI and to describe the an overall picture of the problem space of CDNI and to describe the
relationships among the various components necessary to interconnect relationships among the various components necessary to interconnect
CDNs. CDN Interconnection requires the specification of interfaces CDNs. CDN Interconnection requires the specification of interfaces
and mechanisms to address issues such as request routing, and mechanisms to address issues such as request routing,
distribution metadata exchange, and logging information exchange distribution metadata exchange, and logging information exchange
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 27, 2014. This Internet-Draft will expire on December 1, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 51, line 45 skipping to change at page 51, line 45
the CDN has performed adequately. A CSP may use techniques such as the CDN has performed adequately. A CSP may use techniques such as
client-based metering to verify that accounting information provided client-based metering to verify that accounting information provided
by the CDN is reliable. HTTP conditional requests may be used to by the CDN is reliable. HTTP conditional requests may be used to
provide the CSP with some checks on CDN operation. In other words, provide the CSP with some checks on CDN operation. In other words,
while a CSP may trust a CDN to perform some functions in the short while a CSP may trust a CDN to perform some functions in the short
term, the CSP is able in most cases to verify whether these actions term, the CSP is able in most cases to verify whether these actions
have been performed correctly and to take action (such as moving the have been performed correctly and to take action (such as moving the
content to a different CDN) if the CDN does not live up to content to a different CDN) if the CDN does not live up to
expectations. expectations.
The main trust issue raised by CDNI is that it introduces transitive One of the trust issues raised by CDNI is transitive trust. A CDN
trust. A CDN that has a direct relationship with a CSP can now that has a direct relationship with a CSP can now "outsource" the
"outsource" the delivery of content to another (downstream) CDN. delivery of content to another (downstream) CDN. That CDN may in
That CDN may in term outsource delivery to yet another downstream term outsource delivery to yet another downstream CDN, and so on.
CDN, and so on.
The top level CDN in such a chain of delegation is responsible for The top level CDN in such a chain of delegation is responsible for
ensuring that the requirements of the CSP are met. Failure to do so ensuring that the requirements of the CSP are met. Failure to do so
is presumably just as serious as in the traditional single CDN case. is presumably just as serious as in the traditional single CDN case.
Hence, an upstream CDN is essentially trusting a downstream CDN to Hence, an upstream CDN is essentially trusting a downstream CDN to
perform functions on its behalf in just the same way as a CSP trusts perform functions on its behalf in just the same way as a CSP trusts
a single CDN. Monitoring and reporting can similarly be used to a single CDN. Monitoring and reporting can similarly be used to
verify that the downstream CDN has performed appropriately. However, verify that the downstream CDN has performed appropriately. However,
the introduction of multiple CDNs in the path between CSP and end the introduction of multiple CDNs in the path between CSP and end
user complicates the picture. For example, third party monitoring of user complicates the picture. For example, third party monitoring of
 End of changes. 5 change blocks. 
9 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/