--- 1/draft-ietf-cdni-framework-08.txt 2014-01-30 07:14:35.359789262 -0800 +++ 2/draft-ietf-cdni-framework-09.txt 2014-01-30 07:14:35.495792579 -0800 @@ -1,19 +1,21 @@ -Network Working Group L. Peterson, Ed. +Network Working Group L. Peterson Internet-Draft Akamai Technologies, Inc. Obsoletes: 3466 (if approved) B. Davie Intended status: Informational VMware, Inc. -Expires: July 23, 2014 January 19, 2014 +Expires: August 3, 2014 R. van Brandenburg, Ed. + TNO + January 30, 2014 Framework for CDN Interconnection - draft-ietf-cdni-framework-08 + draft-ietf-cdni-framework-09 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. CDN Interconnection requires the specification of interfaces and mechanisms to address issues such as request routing, distribution metadata exchange, and logging information exchange @@ -30,21 +32,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 23, 2014. + This Internet-Draft will expire on August 3, 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 @@ -254,22 +256,22 @@ interfaces in more detail in Section 4. o CDNI Control interface (CI): Operations to bootstrap and parameterize the other CDNI interfaces, as well as operations to pre-position, revalidate, and purge both metadata and content. The latter subset of operations is sometimes collectively called the "Trigger interface." o CDNI Request Routing interface: Operations to determine what CDN (and optionally what surrogate within a CDN) is to serve end- - user's requests. Is actually a logical bundling of two separate - but related interfaces: + user's requests. This interface is actually a logical bundling of + two separate but related interfaces: * CDNI Footprint & Capabilities Advertisement interface (FCI): Asynchronous operations to exchange routing information (e.g., the network footprint and capabilities served by a given CDN) that enables CDN selection for subsequent user requests; and * CDNI Request Routing Redirection interface (RI): Synchronous operations to select a delivery CDN (surrogate) for a given user request. @@ -279,21 +281,21 @@ availability windows, access control mechanisms, and purge directives. It may include a combination of: * Asynchronous operations to exchange metadata that govern subsequent user requests for content; and * Synchronous operations that govern behavior for a given user request for content. o CDNI Logging interface (LI): Operations that allow interconnected - CDNs to exchange relevant activity logs. May include a + CDNs to exchange relevant activity logs. It may include a combination of: * Real-time exchanges, suitable for runtime traffic monitoring; and * Offline exchanges, suitable for analytics and billing. There is some potential overlap between the set of Trigger-based operations in the CDNI Control interface and the CDNI Metadata interface. For both cases, the information passed from the upstream @@ -464,21 +466,21 @@ | | | | | [Async FCI Push] | (1) | | | | | [MI pre-positioning] | (2) | | | | CONTENT REQUEST | | |-------------------------------------------------->| (3) | | | | | [Sync RI Pull] | (4) | | | - | [RI REPLY] | | + | RI REPLY | | |<--------------------------------------------------| (5) | | | | | | | CONTENT REQUEST | | |------------------------>| | (6) | | | | | [Sync MI Pull] | (7) | | | | | ACQUISITION REQUEST | | X------------------------>| (8) @@ -654,21 +656,21 @@ |------------------------>| | | |(6) | | |DNS op-b-acq.op-a.example| | |------------------------>| | | |(7) | |IPaddr of A's Request Router | |<------------------------| | |HTTP op-b-acq.op-a.example | |------------------------>| | | |(8) - | |302 node2.op-b.acq.op-A.example + | |302 node2.op-b-acq.op-a.example | |<------------------------| | |DNS node2.op-b-acq.op-a.example | |------------------------>| | | |(9) | |IPaddr of A's Delivery Node | |<------------------------| | | | | |HTTP node2.op-b-acq.op-a.example | |------------------------>| | | |(10) @@ -887,21 +889,21 @@ |------------------------>| | | |(5) | | |DNS op-b-acq.op-a.example| | |------------------------>| | | |(6) | |IPaddr of A's Request Router | |<------------------------| | |HTTP op-b-acq.op-a.example | |------------------------>| | | |(7) - | |302 node2.op-b.acq.op-A.example + | |302 node2.op-b-acq.op-a.example | |<------------------------| | |DNS node2.op-b-acq.op-a.example | |------------------------>| | | |(8) | |IPaddr of A's Delivery Node | |<------------------------| | | | | |HTTP node2.op-b-acq.op-a.example | |------------------------>| | | |(9) @@ -2330,23 +2332,22 @@ by the CDNI interfaces. Details of how these interfaces are secured will be specified in the relevant interface documents. 8.2. Digital Rights Management Issues of digital rights management (DRM, also sometimes called digital restrictions management) is often employed for content distributed via CDNs. In general, DRM relies on the CDN to distribute encrypted content, with decryption keys distributed to users by some other means (e.g. directly from the CSP to the end - user.) For this reason, DRM is considered out of scope for the CDNI - WG [RFC6707] and does not introduce additional security issues for - CDNI. + user.) For this reason, DRM is considered out of scope [RFC6707] and + does not introduce additional security issues for CDNI. 9. Contributors The following individuals contributed to this document: o Ray van Brandenburg o Matt Caulfield o Francois le Faucheur @@ -2396,21 +2397,21 @@ [I-D.ietf-cdni-redirection] Danhua, W., Niven-Jenkins, B., He, X., Chen, G., and W. Ni, "Request Routing Redirection Interface for CDN Interconnection", draft-ietf-cdni-redirection-01 (work in progress), October 2013. [I-D.ietf-cdni-requirements] Leung, K. and Y. Lee, "Content Distribution Network Interconnection (CDNI) Requirements", draft-ietf-cdni- - requirements-14 (work in progress), December 2013. + requirements-16 (work in progress), January 2014. [I-D.vandergaast-edns-client-subnet] Contavalli, C., Gaast, W., Leach, S., and E. Lewis, "Client Subnet in DNS Requests", draft-vandergaast-edns- client-subnet-02 (work in progress), July 2013. [RFC3466] Day, M., Cain, B., Tomlinson, G., and P. Rzewski, "A Model for Content Internetworking (CDI)", RFC 3466, February 2003. @@ -2422,25 +2423,34 @@ K., and G. Watson, "Use Cases for Content Delivery Network Interconnection", RFC 6770, November 2012. [RFC6983] van Brandenburg, R., van Deventer, O., Le Faucheur, F., and K. Leung, "Models for HTTP-Adaptive-Streaming-Aware Content Distribution Network Interconnection (CDNI)", RFC 6983, July 2013. Authors' Addresses - Larry Peterson (editor) + Larry Peterson Akamai Technologies, Inc. 8 Cambridge Center Cambridge, MA 02142 USA Email: lapeters@akamai.com Bruce Davie VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 USA Email: bdavie@vmware.com + + Ray van Brandenburg (editor) + TNO + Brassersplein 2 + Delft 2612CT + the Netherlands + + Phone: +31-88-866-7000 + Email: ray.vanbrandenburg@tno.nl