Generic Streaming Requirements Sample Clauses

Generic Streaming Requirements. The requirements in this section 7 apply in all cases where streaming is supported.
AutoNDA by SimpleDocs
Generic Streaming Requirements. The requirements in this section 4 apply in all cases where 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 Streaming Requirements. The requirements in this section 7 apply in all cases where 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. Flash Streaming Requirements The requirements in this section ‎7 only apply if the Adobe Flash product is used to provide the Content Protection System. Adobe RTMPE is approved for streaming using the following Adobe product versions or later: Client side: Flash Player 10.0.22 Server side: FMS 3.51 and FMS 3.03 Licensee will make reasonable commercial efforts to stay up to date with the “then current” versions of the above Adobe products. Progressive downloading of licensed content is prohibited. Flash Encoded Content (including FLV and F4V file formats) must be streamed using Adobe RTMP-E protocol. Flash servers shall be configured such that RTMP-E is enabled, and RTMP is disabled. No content shall be available through both RTMP and RTMP-E. Flash Media Servers shall be configured such that SWF Verification is enabled. Licensee’s and/or its designated CDN shall implement “Token Authentication”, i.e. mechanism that creates a short-lived URL (approx 3-5 minutes) for content by distributing a “token” to the client only at such a time it is authorized to receive the VOD Stream. Licensee must migrate from RTMP-E (stream encryption) to Adobe DRM i.e. Flash Media Rights Management Server successor “Flash Access 2.0” (file-based encryption) or other DRM approved by Licensor in writing within 6 months of the commercial launch of Flash Access 2.0 or such other time as agreed to by the parties and be in full compliance with all content protection provisions herein;. 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 widely commercially available.
Generic Streaming Requirements. The requirements in this section 8. apply in all cases where 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.

Related to Generic Streaming Requirements

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Screening Requirements Xxxxxx shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • ORDERING REQUIREMENTS Eligible Purchasers shall order Goods and/or Services from this Contract, consistent with the terms hereof and by using any ordering mechanism agreeable both to Contractor and Purchaser but including, at a minimum, a purchase order. When practicable, Contractor and Purchaser also shall use telephone orders, email orders, web- based orders, and similar procurement methods (collectively “Purchaser Order”). All Purchase Orders must reference the Contract number. The terms of this Contract shall apply to any Purchase Order and, in the event of any conflict, the terms of this Contract shall prevail. Notwithstanding any provision to the contrary, in no event shall any ‘click-agreement,’ software or web-based application terms and conditions, or any other agreement modify the terms and conditions of this Contract.

  • Bidding Requirements The Advertisement or Invitation to Bid, Instructions to Bidders, Bid security form, if any, and the Bid form with any supplements.

  • Training Requirements Grantee shall:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!