User guide

6-15
Miscellaneous
Figure 6-6: The keys and where they are used on the Creator side
The generated track file of the DCP is encrypted with an AES key that
has been randomly generated by the DVS system. For each track file
one AES key will be created and used. The AES keys are then encrypted
with the public key of the Encryption Key. Afterwards the encrypted
AES keys are written to the KDM file. Of each encrypted track file a
hash value is created which is then written to the PKL file. Next, the
completed CPL, KDM and PKL are signed with the Signing Key. The fin-
ished DCP can then be sent to the Recipient.
The Keys at the Recipient
This diagram shows the keys as they are applied at the Recipient’s site: