LicenseChallengeTeeProperties Enum

Definition

Namespace:

Microsoft.Media.Drm

Assembly:

Microsoft.Media.Drm.RMCore.NETCore.dll

Defines the set of TEE properties the client might support. See TeePropertyList for more information.

public enum LicenseChallengeTeeProperties

type LicenseChallengeTeeProperties = 

Public Enum LicenseChallengeTeeProperties

Inheritance

Enum

LicenseChallengeTeeProperties

Fields

Name	Value	Description
SUPPORTS_HEVC_HW_DECODING	0	The client supports hardware decoding of HEVC content.
SUPPORTS_REMOTE_PROVISIONING	1	The client supports remote provisioning.
SUPPORTS_PRE_PROCESS_ENCRYPTED_DATA	2	The client supports TEE preprocessing of encrypted data. If set, the REE can use DRM_TEE_H264_PreProcessEncryptedData to obtain H.264 slice-header information in the REE for CENCv1 content. This is typically only applicable to certain Microsoft clients.
REQUIRES_PRE_PROCESS_ENCRYPTED_DATA_WITH_FULL_FRAMES	3	When TEE preprocessing of encrypted data is performed on the client, it requires entire frames to be passed to the TEE. If set, the DRM_TEE_H264_PreProcessEncryptedData method requires an entire frame to be passed in at a time. This is typically only applicable to certain Microsoft clients.
REQUIRES_SAMPLE_PROTECTION	4	The client requires sample protection. A sample protection certificate must be passed into the TEE for audio content. This is typically only applicable to certain Microsoft clients.
SUPPORTS_SECURE_CLOCK	5	The client supports a secure clock.
SUPPORTS_SECURE_STOP	6	The client supports secure stop.
SUPPORTS_SECURE_HDCP_TYPE_1	7	The client supports HDCP Type 1 enforcement.
REQUIRES_PREPARE_POLICY_INFO	8	The client requires a call to the TEE PreparePolicyInfo function. If set, the REE must call DRM_TEE_DECRYPT_PreparePolicyInfo to enable a downstream hardware component to obtain the content key and enforce license policy. This is typically only applicable to certain Microsoft clients.
SUPPORTS_DEBUG_TRACING	9	The client supports debug tracing.
REQUIRES_MINIMAL_REVOCATION_DATA	10	The client supports optimizing revocation data size in the TEE at the expense of forward compatibility. The REE will reduce the amount of data it passes across the TEE boundary when ingesting revocation data by only passing the public key from the signing certificate chain instead of the whole chain. The public key is then checked against a fixed allow list before being used to validate the signature on the revocation data. While this reduces memory requirements in the TEE, it means that if a new certificate is ever used to sign revocation lists, the TEE won't be able to use them and will require an update.
SUPPORTS_OPTIMIZED_CONTENT_KEY2	11	The client supports optimized content keys in the TEE. See IncludeOptimizedContentKey2 for more information.