SPEKE Version 2.0 presets

SPEKE Version 2.0 supports the use of multiple, distinct encryption keys for audio and video tracks. MediaPackage uses presets to configure the encryption. The MediaPackage API defines these presets, and they appear in the MediaPackage console in the Video encryption preset and Audio encryption preset menus of the Package Encryption endpoints configuration section. The presets map encryption keys to specific audio or video tracks, based on the number of channels for audio tracks, and based on the video resolution for video tracks. MediaPackage uses specific combinations of audio and video encryption presets to support three different encryption scenarios:

Scenario 1: Unencrypted tracks and encrypted tracks

You can choose not to encrypt the audio or the video tracks by selecting the UNENCRYPTED preset in the Video encryption preset or the Audio encryption preset menus. You can’t select UNENCRYPTED for both audio and video presets, because doing so would mean that you don’t intend to encrypt any of the tracks at all. Also, you can’t combine UNENCRYPTED and SHARED presets for audio and video, because SHARED is a special preset. For more information, see Scenario 2: Single encryption key for all audio and video tracks.

The following list describes valid combinations of UNENCRYPTED presets:

Scenario 2: Single encryption key for all audio and video tracks

The SPEKE Version 2.0 SHARED preset uses a single encryption key for all audio and video tracks, as in SPEKE Version 1.0. When you select the SHARED preset, select it for both audio and video encryption.

Scenario 3: Multiple encryption keys for audio and video tracks

When you use a preset with a name that starts with PRESET-VIDEO- or PRESET-AUDIO-, MediaPackage encrypts the audio tracks and video tracks with the number of encryption keys that the specific preset defines. The following tables show how many keys MediaPackage requests from the key server and how those keys map to tracks. If no track matches the criteria for a particular key, MediaPackage does not use that key to encrypt any track.

MediaPackage encrypts I-frame only trickplay tracks with the key corresponding to their resolution.

In the following table, the Key name value is the value of the ContentKeyUsageRule@IntendedTrackType attribute that MediaPackage uses in the CPIX document. This is sent to the SPEKE server for a specific content key.

In the following table, the Key name value is the value of the ContentKeyUsageRule@IntendedTrackType attribute that MediaPackage uses in the CPIX document. This is sent to the SPEKE server for a specific content key.

Now you know how MediaPackage supports SPEKE Version 2.0 presets for unencrypted tracks and encrypted tracks. With these presets, you can use a single encryption key for all audio and video tracks, and multiple encryption keys for audio and video tracks.