Generic Internet and Mobile Streaming Requirements. The requirements in this section 9 “Generic Internet and Mobile Streaming Requirements”apply in all cases where Internet streaming is supported. Streams shall be encrypted using AES 128 (as specified in NIST FIPS-197) or other robust, industry-accepted algorithm with a cryptographic strength and key length such that it is generally considered computationally infeasible to break. Encryption keys shall not be delivered to clients in a cleartext (un-encrypted) state. The integrity of the streaming client shall be verified before commencing delivery of the stream to the client. Licensee shall use a robust and effective method (for example, short-lived and individualized URLs for the location of streams) to ensure that streams cannot be obtained by unauthorized users. The streaming client shall NOT cache streamed media for later replay but shall delete content once it has been rendered. Apple http live streaming The requirements in this section “Apple http live streaming” only apply if Apple http live streaming is used to provide the Content Protection System. Use of Approved DRM for HLS key management. Licensee shall NOT use the Apple-provisioned key management and storage for http live streaming (“HLS”) (implementations of which are not governed by any compliance and robustness rules nor any legal framework ensuring implementations meet these rules) for protection of Licensor content between Licensee servers and end user devices but shall use (for the protection of keys used to encrypt HLS streams) an industry accepted DRM or secure streaming method approved by Licensor under section 2 of this Schedule. Http live streaming on iOS devices may be implemented either using applications or using the provisioned Safari browser, subject to requirement “Use of Approved DRM for HLS Key Management” above. Where the provisioned HLS implementation is used (e.g. so that native media processing can be used), the connection between the approved DRM client and the native HLS implementation shall be robustly and effectively secured (e.g. by mutual authentication of the approved DRM client and the native HLS implementation). The m3u8 manifest file shall only be delivered to requesting clients/applications that have been authenticated as being an authorized client/application. The streams shall be encrypted using AES-128 encryption (that is, the METHOD for EXT-X-KEY shall be ‘AES-128’). The content encryption key shall be delivered via SSL (i.e. the URI for EXT-X-KEY, the URL u...
Generic Internet and Mobile Streaming Requirements. The requirements in this section “Generic Internet and Mobile Streaming Requirements” apply in all cases where Internet streaming is supported. Except for the first 2 minutes, 13 seconds of consecutive footage, encryption shall be applied to the entirety of A/V data in accordance with this schedule. The streaming client shall NOT store streamed media after the playback session has ended except as set forth in section 3.2 (Instant Playback). Any storage of streamed media shall be under the protection of an Approved Content Protection System.. Implementation of an Approved Content Protecton System on iOS The requirements in this section “Implementation of an Approved Content Protecton System on iOS” only apply for implementations of an Approved Content Protection System on iOS devices. The connection between the approved DRM client and the native Quicktime player shall be secured via a cryptographically secure mutual authentication. The streams between the approved DRM client and the native Quicktime player shall be encrypted using AES-128.. Output of the stream from the receiving device shall not be permitted unless this is explicitly allowed elsewhere in the schedule. Output of the Licensed Content over AirPlay Streaming is allowed in Standard Definition if AirPlay Link Encryption is used to protect interactions between the iOS device and the Apple TV, provided that Amazon may not output Licensed Content via AirPlay Streaming as set forth in this subsection unless Amazon has approval for such output from three Major Studios with respect to feature films licensed by such Major Studios for distribution on the Service. The client shall NOT cache streamed media for later replay iOS applications shall include functionality which detects if the iOS device on which they execute has been “jailbroken” and shall disable all access to protected content and keys if the device has been jailbroken, provided that Amazon may deliver Included Programs to iOS devices without detecting if iOS devices are jailbroken as set forth in this subsection if Amazon has approval for such delivery from three Major Studios with respect to content licensed from such Major Studios for distribution on the Service. Pre-Approved Hardware Based Streaming Formats: Real Time Messaging Protocol Encrypted (RTMPe) enabled by Flash Media Server version 3.06 or later. Amazon may use RTMPe in connection with Hardware-Based DRM Streaming Devices only that were manufactured on or prior to December 31, ...
Generic Internet and Mobile Streaming Requirements. The requirements in this Section 2 shall apply in all cases when Included Programs are distributed via Internet Streaming.
Generic Internet and Mobile Streaming Requirements. The requirements in this section 9 “Generic Internet and Mobile Streaming Requirements”apply in all cases where Internet streaming is supported.
Generic Internet and Mobile Streaming Requirements. The requirements in this Section 2 shall apply in all cases when Included Programs are distributed via Internet Streaming. Streams shall be encrypted using (a) AES 128 (as specified in NIST FIPS-197) or (b) other robust, industry-accepted algorithm with a cryptographic strength and key length such that it is generally considered at least as robust as AES 128. Encryption keys shall not be delivered to clients in a cleartext (un-encrypted) state. The integrity of the Streaming client shall be verified before permitting playback functionality for the Streaming of the Included Program. Comcast shall use a robust and effective method (for example, short-lived and individualized URLs for the location of streams) to ensure that streams cannot be obtained by unauthorized users for playback in a manner not permitted by this Agreement. For Streamed Included Programs, Comcast shall NOT configure the playback client to cache Streamed media for later replay (i.e., playback after the Included Program is complete), but shall configure the playback client to not permit playback of any cached portion of the Included Program once it has been completed.
