Open Caching

Delivering a great video experience requires content to be served as close to the end-user as possible. In this whitepaper, we illustrate how network operators can implement Open Caching nodes at the edge of their network, while adhering to specifications created by the Open Caching Working Group of the Streaming Video Alliance. These nodes can mitigate delivery latency and provide an improved viewer experience when hosted by the ISP and connected to the CDN/Content Provider nodes outside of the operator network, to create an Open Caching Network.

Problem statement and functional requirements of an open caching solution deployed by service providers to be used by content providers and content delivery networks.

This document specifies requirements for Open Caching System (OCS) for Logging data to help track data acquisition and delivery of it to the end user. The information logging is critical for the Open Caching Nodes as well as the upstream CDN and the Content Provider (CP). Logging information helps OCS track key performance metrics such as, data acquisition, delivery success and failures, measuring of effective throughput, cache hits and for troubleshooting fault and performance degradation. The logging data provided to the CDN by the OCS is also used by CDNs for auditing, billing and SLA purposes. The information logging will also be used by Open Caching Nodes (making up an OCS) for ensuring its compliance of SLAs with CDNs and measuring and assuring Quality of Experience (QoE) for an end user.

This document describes the process of provisioning a Logging Integration between a CDN and an ISP in an Open Caching solution. That is the process of configuring how delivery logs are transferred from ISP to CDN. The requirements for logging in Open Caching Nodes are described in the “Open Caching Logging Requirements Specification” document. This document defines extensions to the “Footprint and Capabilities” interface and to the “Service Metadata” interface, to allow provisioning a Logging Integration.

This includes the functional specification of open-caching service provisioning interfaces enabling a CDN and an SP to exchange information to enable the delegation of CDN content requests to the SP Open Caching system.

This document describes the high-level functional specification of open caching request routing and the required interfaces to enable request routing to be performed from an upstream CDN to an open cache system. This version has been updated to address the Manifest Rewrite routing scheme.

This document describes the functional specification of the Open Caching Content Management interface and the functionality requirements from the SP Open Caching system. This document discusses the interface between the SP Open Caching Controller and the CDN. The interface between the SP OCC and the cache nodes (OCNs) is beyond the scope of this document.

This document describes the functional specification of open-caching relayed-token-authentication mechanism. The focus is on generically supporting URI signing using this method. There are additional applications – like user Cookies, which are mentioned in this document without getting into the specifics. While multiple different CDNs, as well as CDNi, support Tokenization in alternative methods, the goal of this implementation is to support all of these different formats via the relay authentication mechanism.

This document outlines measurement metrics for open-caching. The focus of this document is to outline key performance indicators related to quality of service metrics at the open cache nodes that is responsible for delivering the streaming content.

This is the first part in a set of documents that specifies the motivational drivers, use cases, and standards for a configuration interface to facilitate interoperability within the content delivery network (CDN) and open caching ecosystems. This document set presents a layered architecture that extends the Internet Engineering Task Force (IETF) CDN Interconnect (CDNi) metadata model and adds publishing layer Application Programming Interfaces (APIs) to provide configuration management capabilities required by the CDN and open caching industries.

This is part two in a set of documents that specifies the motivational drivers, use cases, and standards for a configuration interface to facilitate interoperability within the content delivery network (CDN) and open caching ecosystem. This document presents the context and requirements for extending the Content Delivery Network Interconnection (CDNi) metadata model, as well as specific extensions that will fulfill those requirements.

This document will provide all the necessary information for an Internet Engineering Task Force (IETF) memo describing the Streaming Video Alliance (SVA) metadata interface requirements beyond those stated in RFC-7337 (Content Distribution Network Interconnection Requirements), along with requested extensions to RFC-8006 (Content Delivery Network Interconnection Metadata).

This is part three in a set of documents that specifies the motivations, use cases, and standards for a configuration interface to facilitate interoperability within the content delivery network (CDN) and open caching ecosystems. In this document, the requirements for a configuration publishing layer are presented, along with APIs that facilitate the publishing of CDNi metadata objects within the CDN and open caching ecosystems.

This document describes the high-level functional specification of open caching request routing and the required interfaces to enable request routing to be performed from an upstream CDN to an open cache system. This is version 1 of the document.

Content delivery delegation in open caching can be realized through two modes of request redirection, iterative and recursive.

Open caching previously supported the iterative mode only. This document describes the data model and architecture changes required to enable the recursive mode of delegation as well.

This document describes the Application Programming Interface (API) methods and data model related to the Footprint and Capabilities Interface. The API has been entirely designed by the SVTA Open Caching group whereas the data model is based on the IETF Content Delivery Network Interconnection (CDNi) work. and on extensions specified by the SVTA Open Caching group.