Common use of Generic Internet Streaming Requirements Clause in Contracts

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 2 apply in all cases. 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 shall not be delivered to clients in a cleartext (un-encrypted) state. 2.3. The integrity of the streaming client shall be verified by the streaming server 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.

Generic Internet Streaming Requirements. The requirements in this section 2 Error: Reference source not found apply in all casescases where Internet streaming is supported. 7.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. 7.2. Encryption keys shall not be delivered to clients in a cleartext (un-encrypted) state. 7.3. The integrity of the streaming client shall be verified by the streaming server before commencing delivery of the stream to the client. 7.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.

Generic Internet Streaming Requirements. The requirements in this section 2 apply in all cases. 2.1. Streams shall be encrypted using AES 128 (as specified in NIST FIPS-197) or other robust, industry-accepted algorithm (e.g., DES, SSL), with a cryptographic strength and key length such that it is generally considered computationally infeasible to break. 2.2. Encryption keys shall not be delivered to clients in a cleartext (un-encrypted) state. 2.3. The integrity of the streaming client shall be verified by the streaming server 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.

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-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.