Common use of Microsoft Silverlight Clause in Contracts

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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 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) to use (for the protection of keys used to encrypt HLS streams) 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 shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. 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.

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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 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) to use (for the protection of keys used to encrypt HLS streams) 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 shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. iOS applications shall include functionality which whith 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.

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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 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) to use (for the protection of keys used to encrypt HLS streams) 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. timeframeby end of February 28th, 2014.. 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 shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’)) except for temporary caching or buffering which shall not last beyond the viewing of the program. iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. 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.

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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. Use of Approved DRM for HLS key management. Licensee shall migrate from fromNOT use of 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) to tofor protection of Licensor content between Licensee servers and end user devices but shall use (for the protection of keys used to encrypt HLS streams) of an industry accepted DRM or secure streaming method which is governed governedapproved by compliance and robustness rules and an associated legal framework, within a mutually agreed timeframetimeframeLicensor 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 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). Licensor content shall NOT be transmitted over Apple Airplay and applications shall disable use of Apple Airplay. The client shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. 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.

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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 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) to use (for the protection of keys used to encrypt HLS streams) 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 shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. 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.

Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” 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 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) to use (for the protection of keys used to encrypt HLS streams) 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 shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as possible. 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. REVOCATION AND RENEWAL The Licensee shall use reasonably commercialcommercially reasonable efforts to ensure that it has have a policy in place which ensures that clients and servers of the Content Protection System are promptly and securely updated, and where necessary, revoked, in the event of a security breach (that can be rectified using a remote update) being found in the Content Protection System and/or its implementations in clients and servers. Licensee shall use reasonably commercialcommercially reasonable efforts to ensure that it has have a policy in place which ensures that patches including System Renewability Messages received from content protection technology providers (e.g. DRM providers) and content providers are promptly applied to clients and servers. ACCOUNT AUTHORIZATION Content Delivery. Content, licenses, control words and ECM’s shall only be delivered from a network service to registered devices associated with an account with verified credentials. Account credentials must be transmitted securely to ensure privacy and protection against attacks.