DCI Specs - Digital Cinema Initiatives

More documents

Recommendations

Info

The above RSA asymmetric protection, AES (with 128-bit keys) or TDES (with 112-bit key)symmetric ciphers, may be used to protect the storage of keys once decrypted from theKDM within a Media Block (e.g., where off-secure-chip memory is used for key cachingwithin a Media Decryptor, for example).9.7.5. Integrity Check CodesData integrity signatures (hash values) shall be generated/calculated according to thePKCS-1 Digital Signature Standard, as specified in [IETF RFC 3447 (RSA and SHA-256)].All signatures shall use SHA-256. Digital Certificates in X.509v3 format as constrainedaccording to Section 9.8., shall be used to authenticate signatures. Signature elementdefinitions and other signature details are available in the specification for each signed datastructure.Cryptographic data integrity checksums shall be ensured according to the HMAC-SHA-1algorithm, as specified in [FIPS PUB 198a “The Keyed-Hash Message AuthenticationCode.”]9.7.6. Key Generation and DerivationAsymmetric keys (RSA keys) shall be generated as specified in [IETF RFC 3447].Symmetric key generation shall be per ANSI X9.31.A vendor that pre-loads an RSA private key into a device (e.g., secure silicon per Section9.5.2.2 Physical Security of Sensitive Data) shall ensure that these pre-loaded keys areunique to each device made by that vendor. The vendor shall not keep any record of thepreloaded private keys, though they can keep records of the matching public keys. RSAkeys shall be 2048 bits in length, and may be generated from two or three prime numbers,each of which must be at least 680 bits long. The mechanism used to generate RSA keypairs must have at least 128-bits of entropy (unpredictability).A vendor that pre-loads an AES or TDES symmetric key into a device shall generate eachkey with a high quality random number generator with at least 128 bits of entropy (112 bitsfor TDES). The vendor may not keep any records of these symmetric keys.9.7.7. Numbers of KeysNo more than 256 keys should be used to encrypt the essence of a single composition (i.e.,Composition Playlist). To support multiple shows, Media Decryptors should be capable ofsecurely caching at least 512 keys. The Show Playlists may be comprised of multiplecompositions.9.8. Digital Certificate, Extra-Theater Messages (ETM), and KeyDelivery Messages (KDM) RequirementsThe following Society of Motion Picture and Television Engineers (SMPTE) published standardsshall be utilized:1. SMPTE430-1: D-Cinema Operations- Key Delivery Message (SMPTE3383B),2. SMPTE430-2: D-Cinema Operation- Digital Certificate (SMPTE3384B), and3. SMPTE430-3: D-Cinema Operations- Generic Extra-Theater Message Format(SMPTE3385B).Note: Portions of the SMPTE standards are incomplete with respect to many behaviorrequirements, the subjects of which are typically addressed by SMPTE as "Informative notes."DCI Digital Cinema System Specification v.1.2 Page 148
Other sections of this DCI Specification identify normative requirements that shall takeprecedence over SMPTE "Informative notes."DCI Digital Cinema System Specification v.1.2 Page 149
Page 1 and 2:
Digital Cinema Initiatives, LLCDigi
Page 3 and 4:
Table of Contents1. OVERVIEW 151.1.
Page 5 and 6:
5.2.2. Packaging Fundamental Requir
Page 8 and 9:
7.5.5.1. Introduction..............
Page 10 and 11:
9.4.2.5. Screen Management System (
Page 12 and 13:
Table of FiguresFigure 1: System Ov
Page 14 and 15:
THIS PAGE LEFT BLANK INTENTIONALLYD
Page 16 and 17:
equirements for encrypting the esse
Page 18 and 19:
• This document specifies a basel
Page 20 and 21:
DCI Digital Cinema System Specifica
Page 22 and 23:
2.1.1. Major System Concepts2.1.1.1
Page 24 and 25:
2.1.1.8. ReelsFeature films have be
Page 26 and 27:
Metadata within the DCDM provides a
Page 28 and 29:
3.2.1.6. Transfer FunctionThe CIE X
Page 30 and 31:
The information, as shown in Table
Page 32 and 33:
AES Pair#/Ch# Channel # Label / Nam
Page 34 and 35:
3.3.4. File Format3.3.4.1. GeneralT
Page 36 and 37:
3.4.3. Timed Text Concepts and Requ
Page 38 and 39:
Page 40 and 41:
• All decoders shall decode each
Page 42 and 43:
Page 44 and 45:
5.2.2.3. InteroperableThe Packaging
Page 46 and 47:
Figure 6: Example Show PlaylistThe
Page 48 and 49:
Length (Value Length), followed by
Page 50 and 51:
which it was stopped or paused. It
Page 52 and 53:
5.3.4.2. Frame BoundariesThe Audio
Page 54 and 55:
• Rating• Aspect Ratio• Image
Page 56 and 57:
• Annotation Text parameter (opti
Page 58 and 59:
Page 60 and 61:
7.2.3.1. ReliabilityA key part of t
Page 62 and 63:
• Country• Rating• Aspect Rat
Page 64 and 65:
facility, while the system is in op
Page 66 and 67:
Exhibitor and the Distributor, data
Page 68 and 69:
7.5.2.2. Ingest InterfacesExcept fo
Page 70 and 71:
(channels) * hours * 60 min/hour *
Page 72 and 73:
7.5.4.2.4. UnpackagingAny packaged
Page 74 and 75:
7.5.6. Audio System7.5.6.1. Introdu
Page 76 and 77:
made up of Theater System devices a
Page 78 and 79:
DCI Digital Cinema System Specifica
Page 80 and 81:
8.2.2.3. Alternative ContentThe pro
Page 82 and 83:
With the projector turned off or wi
Page 84 and 85:
Image ParametersNominal(Projected I
Page 86 and 87:
Input Code Values Output Chromatici
Page 88 and 89:
8.4. Projector Interfaces8.4.1. Int
Page 90 and 91:
• Lens Shift Up / Down• Lamp Mo
Page 92 and 93:
• Essence Encryption and Cryptogr
Page 94 and 95:
content keys and Trusted Device Lis
Page 96 and 97:
Figure 14: Digital Cinema Security
Page 98 and 99: Figure 15 presents the two fundamen
Page 100 and 101: DCI Digital Cinema System Specifica
Page 102 and 103: 9.4.2.3. Media Blocks (MBs)The term
Page 104 and 105: which TLS-based authentication alon
Page 106 and 107: working with the security infrastru
Page 108 and 109: Figure 18: Show Playback Overview9.
Page 110 and 111: a. Playout shall be fully supported
Page 112 and 113: 9.4.5. Intra-Theater Communications
Page 114 and 115: 4. Projector SPB designs shall not
Page 116 and 117: the event, and zero all Critical Se
Page 118 and 119: window) shall be UTC.Security Manag
Page 120 and 121: . The SM shall independently authen
Page 122 and 123: 6. No broadcast RRP commands shall
Page 124 and 125: Functions of the Security Manager (
Page 126 and 127: Note: DCI reserves the right, at so
Page 128 and 129: • Is required to survive camcorde
Page 130 and 131: • Log Data - Security event infor
Page 132 and 133: using the GetEventList and GetEvent
Page 134 and 135: failure) per Section 9.6.1.3 Digita
Page 136 and 137: • Secure Silicon -Sensitive data
Page 138 and 139: secure silicon chip, input/output s
Page 140 and 141: FIPS 140-2 level 3 devices provide
Page 142 and 143: to the appropriate Section 9.4.5.2.
Page 144 and 145: those under the control of the Secu
Page 146 and 147: Security Managers (SMs) other than
Page 150 and 151: THIS PAGE LEFT BLANK INTENTIONALLYD
Page 152 and 153: CPRL Acronym for Component Position
Page 154 and 155: LTCMain TitlesMBMDMEMetadataMTBFMXF
Page 156: TDLTimed TextTLMTLSTMSTrack FileUDP
show all

DCI Specs - Digital Cinema Initiatives

Create successful ePaper yourself

Delete template?

Save as template?