What is Open Caching?
A New Approach for Streaming:
Many Caches, All Connected
Since the beginning of streaming video, caches have been largely proprietary. Even when developed using open source technologies, like Squid, companies often made unique enhancements and developed their own approaches to hierarchies, session windows, and even the OS TCP stack. Now, with most streaming operators employing multiple CDNs, managing all of the caches across the different networks from a single interface is extremely complex. Open Caching is an attempt to level the paying field so content rights holders, network operators, and CDNs all have visibility into the caching network.
Click on a box to get more detail about the Open Caching component.
Enabling Caching Interoperability
Three key components make up an Open Caching Network.
An Open Caching Node represents a caching server, within a content delivery architecture, that complies with Open Caching specifications. The cache can either be built using the specifications (such as for an ISP implementing Open Caching at the edge of their network), or Open Caching functionality can be added through plugins or other means (such as for a Content Delivery Network caches or OTT Platform origins).
The Request Router handles the inbound request for content and forwards this request to the appropriate caching node within an environment. The Open Caching specifications identify three methods of routing: DNS, HTTP, and Manifest.
The Control Plane handles all communication related to management of configurations, content purging and pre-positioning, logging, and security. While the Request workflow is focused on the end user’s ability to retrieve content, the Control Plane is focused on how the different members of the video distribution chain are empowered to partake in the delivery process.
The Industry is Beginning to Notice
Open Caching Implementations
Open Caching Configuration Interface: Part 3 – Publishing Layer APIs (Version 1.1)
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.