The guidelines, published as Version 0.9, specify support for both live and on-demand services, and crucially give detail of how different encoding profiles are linked to interoperability points needed for conformance testing.
One main area of clarification concerns end to end content security around the DRM and encryption. DASH unifies encryption around the Common Encryption (‘cenc’) protection scheme, to enable interoperability and avoid having to support multiple encryption methods, which would increase device processing costs. But all along DASH has avoided specifying an end to end end-to-end DRM so that vendors and service providers can choose their own. So DASH 264 provides a framework for multiple DRMs to protect a content file by adding instructions or relevant proprietary information in predetermined locations to a file that is encrypted with Common Encryption. This then specifies encryption parameters that can be applied by a scrambling system and key mapping methods based on a common key identification scheme.
The point of this single key identification scheme is that it enables the same encrypted version of a file to be used by different DRMs. The new guidelines reduce the encryption parameters and associated metadata to specific use cases for VOD and live content, simplifying the overall system and again improving prospects for interoperability.