Generic Internet Streaming Requirements. The requirements in this section 3 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.
Generic Internet Streaming Requirements. The requirements in this section 5 apply in all cases where Internet streaming is supported.
5.1. 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.
5.2. Encryption keys shall not be delivered to clients in a cleartext (un-encrypted) state.
5.3. The integrity of the streaming client shall be verified before commencing delivery of the stream to the client.
5.4. 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.
5.5. The streaming client shall NOT cache streamed media for later replay but shall delete content once it has been rendered.
Generic Internet Streaming Requirements. The requirements in this section 7 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 by the streaming server 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. The requirements in this section 8 only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version. When used as part of a streaming service only (with no download), Playready licenses shall only be of the the SimpleNonPersistent license class. If Licensor uses Silverlight 3 or earlier version, within 4 months of the commencement of this Agreement, Licensee shall migrate to Silverlight 4 (or alternative Licensor-approved system) and be in full compliance with all content protection provisions herein. The requirements in this section “Apple http live streaming” only apply if Apple http live streaming is used to provide the Content Protection System. Licensee shall migrate from use of http live streaming (implementations of which are not governed by any compliance and robustness rules nor any legal framework ensuring implementations meet these rules) to use of an industry accepted DRM or secure streaming method which is governed by compliance and robustness rules and an associated legal framework, within a mutually agreed timeframe. Http live streaming on iOS devices may be implemented either using applications or using the provisioned Safari browser. The URL from which the m3u8 manifest file is requested shall be unique to each requesting client. The m3u8 manifest file shall only be delivered to requesting clients/applications that have been authenticated in some way as being an authorized client/application. The streams shall be encrypted using AES-128 encryption (that is, the METHOD fo...
Generic Internet Streaming Requirements. The requirements in this section 2 apply in all cases. 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 by the streaming server 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.
Generic Internet Streaming Requirements. The requirements in this section 3 apply in all cases where Internet streaming is supported.
Generic Internet Streaming Requirements. The requirements in this section 8. 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 except only with respect to temporary caching and buffering which shall not last beyond the viewing of the program.
Generic Internet Streaming Requirements. The requirements in this section 0 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 by the streaming server 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 requirements in this section 8 only apply if the Adobe Flash product is used to provide the Content Protection System. Adobe Flash Access 2.0 or later versions of this product are approved for streaming. Licensee must make reasonable commercial efforts to comply with Adobe compliance and robustness rules for Flash Server products at such a time when they become commercially available. The requirements in this section 9 only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version. When used as part of a streaming service only (with no download), Playready licenses shall only be of the the SimpleNonPersistent license class. If Licensor uses Silverlight 3 or earlier version, within 4 months of the commencement of this Agreement, Licensee shall migrate to Silverlight 4 (or alternative Licensor-approved system) and be in full compliance with all content protection provisions herein.
Generic Internet Streaming Requirements. The requirements in this section 2 apply in all cases where Internet streaming is supported. 0212 PPV-VOD License Agreement-iND comments to Sony v3.doc – iND comments to Sony v2
2.1. 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.
2.2. Encryption keys that are critical to the strength of the Content Protection System shall not be delivered to clients in a cleartext (un-encrypted) state.
2.3. The integrity of the streaming client shall be verified before commencing delivery of the stream to the client.
2.4. 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.
2.5. The streaming client shall NOT cache streamed media for later replay but shall delete content once it has been rendered.
Generic Internet Streaming Requirements. The requirements in this section 3 apply in all cases where Internet streaming is supported.
3.1. 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.
3.2. Encryption keys that are critical to the cryptographic strength of the Encryption shall not be delivered to clients in a cleartext (un-encrypted) state.
3.3. The integrity of the streaming client shall be verified before commencing delivery of the stream to the client.
3.4. 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.
3.5. The streaming client shall NOT cache streamed media for later replay but shall delete content once it has been rendered.
Generic Internet Streaming Requirements. The requirements in this section 73 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. The requirements in this section 84 only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version. The requirements in this section “Apple http live streaming” only apply if Apple http live streaming is used to provide the Content Protection System. Licensee shall migrate from use of http live streaming (implementations of which are not governed by any compliance and robustness rules nor any legal framework ensuring implementations meet these rules) to use of an industry accepted DRM or secure streaming method which is governed by compliance and robustness rules and an associated legal framework, within a mutually agreed timeframe. Http live streaming on iOS devices may be implemented either using applications or using the provisioned Safari browser. The URL from which the m3u8 manifest file is requested shall be unique to each requesting client. The m3u8 manifest file shall only be delivered to requesting clients/applications that have been authenticated in some way 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 used to request the content encryption key, shall be a https URL). Output of the stream from the receiving device shall not be permitted unless this is explicitly allowed elsewhere in the schedule. No APIs that permit stream output shall be used in applications (where applications are used). The client ...
