Generic Internet Streaming Requirements Sample Clauses

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.
AutoNDA by SimpleDocs
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 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.
AutoNDA by SimpleDocs
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 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.

Related to Generic Internet Streaming Requirements

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

  • Licensing Requirements (a) Employer and Employee hereby covenant and agree that this Agreement and/or Employee’s employment may be subject to the approval of one or more gaming regulatory authorities (the “Authorities”) pursuant to the provisions of the relevant gaming regulatory statutes (the “Gaming Acts”) and the regulations promulgated thereunder (the “Gaming Regulations”). Employer and Employee hereby covenant and agree to use their best efforts to obtain any and all approvals required by the Gaming Acts and/or Gaming Regulations. In the event that (i) an approval of this Agreement or Employee’s employment by the Authorities is required for Employee to carry out Employee’s duties and responsibilities set forth in Section 3 of this Agreement, (ii) Employer and Employee have used their best efforts to obtain such approval, and (iii) this Agreement or Employee’s employment is not so approved by the Authorities, then this Agreement shall immediately terminate and shall be null and void, thus extinguishing any and all obligations of either party, subject to any surviving obligations of Employee under Sections 9, 10 and 21. (b) If applicable, Employer and Employee hereby covenant and agree that, in order for Employee to discharge the duties required under this Agreement, Employee must apply for or hold a license, registration, permit or other approval (the “License”) as issued by the Authorities pursuant to the terms of the relevant Gaming Act and as otherwise required by this Agreement. In the event Employee fails to apply for and secure, or the Authorities refuse to issue or renew Employee’s License, Employee, at Employer’s sole cost and expense, shall promptly defend such action and shall take such reasonable steps as may be required to either remove the objections or secure or reinstate the Authorities’ approval, respectively. The foregoing notwithstanding, if the source of the objections or the Authorities’ refusal to renew or maintain Employee’s License arise as a result of any of the acts, omissions or events described in Section 1(c) of this Agreement, then Employer’s obligations under this Section 8 also shall not be operative and Employee shall promptly reimburse Employer upon demand for any expenses incurred by Employer pursuant to this Section 8. (c) Employer and Employee hereby covenant and agree that the provisions of this Section 8 shall apply in the event Employee’s duties require that Employee also be licensed by governmental agencies other than the Authorities.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Trunking Requirements The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Transmission and Routing of Telephone Exchange Service Traffic 50.4.1 The Appendix Reciprocal Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the Appendix ITR, which is/are attached hereto and incorporated herein by reference.

  • COMPLIANCE WITH LICENSING REQUIREMENTS CONTRACTOR shall comply with all necessary licensing requirements and shall obtain appropriate licenses and display the same in a location that is reasonably conspicuous, as well as file copies of same with the County Executive Office.

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