DCI Specs - Digital Cinema Initiatives

More documents

Recommendations

Info

Functions of the Security Manager (SM), Item 9.b.9.4.5.3.3. Intra-Theater Network Housekeeping Messages9.4.5.3.3.1. TermTLSThis command, TermTLS, generates an RRP from SM to Secure ProcessingBlock (SPB) commanding termination of the Transport Layer Security (TLS)session. The RRP is executed under TLS, after which the SPB zeros all TLSsession parameters.RRP Requester RespondentSuccessful TLS session terminated TLS session terminated; resources freedUnsuccessful Error eventTable 16: RRP State: TermTLSNotes:• Transport Layer Security (TLS) layer termination process closes the underlyingTCP/IP connection.9.4.5.3.3.2. AlertThis command, Alert, is a Non-TLS UDP/IP RRP from an Secure ProcessingBlock (SPB) to an SM, or from Security Manager to Screen ManagementSystem, issued in the event of a security alarm under circumstances when (forwhatever reason) a Transport Layer Security (TLS) session and normal RRPresponses are not available to deliver the alarm.The need for this command may arise from the failure of a device, power, ornetwork. Recognizing that UDP/IP does not guarantee reliable delivery, therequester should send the command at least three times. If there is no response,a network problem should be assumed. The responder should respondidentically to each request it receives.RRP Requester RespondentSuccessful SE receives response and knowsSM received requestSM is aware of alert, (but unaware ifresponse received)Unsuccessful SE is unaware whether SM is awareof error conditionSM may or may not be aware ofrequestUnsuccessfulafter repeatsFollow error proceduresSM may or may not be aware ofrequestTable 17: RRP State: AlertNotes:• If the need for this RRP is caused by a network problem, lower level TCPcommunications may have knowledge about the error conditions. These need tobe woven into the ITM problem discovery/recovery process.• Conditions/protections for the issuance of this command must include:• Protection of the network from being jammed if the problem is with the SPB.• SPBs TLS recovery expectations, and behavior if recovery doesn’t happen.• Behavior of SPBs prior to being communicated to (e.g., power-up).DCI Digital Cinema System Specification v.1.2 Page 124
• This RRP can be used by the SMS to direct an SM to initiate a TLS (re)connect,though this may be done also at the TCP layer.9.4.5.3.3.3. AbortThis command, Abort, terminates an open RRP that is: 1) instigated by theoriginal recipient’s lack of response, or 2) forced by the original recipient.The Abort command interrupts an open RRP by interjecting the abort before theoriginal recipient responds. The recipient of any RRP can issue this commandresponse in place of the originally requested response. No parameters are sentin either the request or response.RRP Requester RespondentSuccessful SM (or SMS) no longer is waiting forRRP(id) responseSE (or SM) aborts its RRP(id)response ambitionsUnsuccessful Error eventDCI Digital Cinema System Specification v.1.2 Page 125Table 18: RRP State: AbortNotes:• It shall not be permitted for an SE to abort a QuerySPB RRP.• The responder must respond to the Abort request, even if the original RRP(id)response happens to have been sent (race condition is OK).9.4.6. ForensicsForensics do not prevent content theft or other compromises, but rather, it provides methodsfor their detection and investigation. Forensic features deter attackers who are aware thattheir actions would be logged and/or reported in considerable detail.Forensic features fall into two classes: Forensic Marking (FM) and logging. Forensic Markingembeds tracking information into content itself, to be carried into subsequent legitimate orstolen copies. Logging creates records of both normal and abnormal events in theDistribution and Exhibition process. During a content theft investigation, both FM andlogging information may be combined to establish the details of the security compromise.Industry terminology for watermarking and Forensic Marking is not consistent. For thesesecurity specification purposes, stakeholders have agreed to use the term Forensic Markingfor all content marks.9.4.6.1. Forensic MarkingThese specifications require that image and audio Forensic Marking (FM) capability beincluded in each Image Media Block.The security system identifies content markingdevices (e.g., Forensic Marking embedders) as the “FM” Security Entity (SE) type. Tosupport FM processes, standardized Intra-Theater Messaging (ITM) may be used whereneeded for communications between such SEs and Security Managers (SMs). Suchcommunications and associated FM behavior is outside of this specification. Howeverthe requirements of ITM Section 9.4.5 Intra-Theater Communications shall be mandatorywhere such theater messaging employs the intra-auditorium security network. ForensicMarking does not require interoperability between detection systems, as the detectionoperation is usually performed “off line” as part of a security investigation.Multiple solutions may be qualified and will allow Media Block solutions providers toselect the solution of their choice. Candidate providers should meet with individualstudios to discuss RAND and technical suitability of their approach.
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 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 148 and 149: The above RSA asymmetric protection
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?