Inter-Society Digital Cinema Forum (ISDCF)

While the transition to SMPTE DCP is set for April 2010, it will take time for the transition to complete. An important part of this transition is the inclusion of accessibility features in digital cinema systems. The DCI specification, which is the baseline specification for SMPTE DCP, calls for open subtitles. But thanks to the support of NATO and the many manufacturers who have contributed, SMPTE DCP standards also include accessibility features such as separately identifiable open captions, closed captions, and multi-channel audio formats that include Hearing Impaired (HI) and Visually Impaired Narrative (VI-N) audio. The document below is the most recent work that describes the timeline for implementation of SMPTE DCP, including accessibility features.

2009-11-11 Timeline for Accessibility.pdf

The documents below capture early thinking towards managing KDM distribution, including the use of the Cinema Communication Message (formerly Cinema Control Message), or CCM. The CCM is not about control, as the name may imply. Instead, it is a message type for carrying payloads such as KDMs (Key Delivery Messages), FLMs (Facility List Messages), and logs. Ideas are presented for using the CCM with a web services framework and with SMTP. These documents are a snapshot of work-in-discussion, and posted here to inform the many developers of digital cinema systems of this effort. These topics move quickly, and may have advanced beyond what has been recorded in document form. Please contact ISDCF to participate in this work.

SMTP feature set 0.1.pdf
KDM Distribution Portal (draft v2).pdf
CCM resurrection package.zip
2009-1-13 CCM_SOAP.pdf

Facility Identifiers provide the mechanism for a unique ID for a theatre location. Facility identifiers are required with the SMPTE 430-7 Facility List Message (FLM), an important message type in the automation of security key management. The entity that manages the identifier may be the theatre owner or designated representative. It is logical that the UUID could become the identifier of choice as it requires no registry. However, an additional problem is that there are multiple identifiers managed by multiple entities for the same location. Because of this, it"s useful to know whose identifier one is looking at. For this purpose, the proposal below outlines an identifier scheme presented to ISDCF. It is proposed that the scheme be formalized as a unique name type under the Uniform Resource Name (URN) standard naming scheme managed by the IETF.

2008-6-16 Facility Identifiers - NATO.pdf

KDMs arrive in theatres from many sources, typically by email. Theatre operators have a difficult time sorting and identifying the emails and files that are sent. The KDM Naming Convention is the recommended naming scheme for ZIP files containing KDMs, and for the KDM filename itself. It is based on the many of the name types used in the Digital Cinema Naming Convention (see below). This naming scheme is still evolving, so users should check back for updates. The KDM Naming Convention is described at kdmNamingConvention.com.

The content name displayed by digital cinema servers can become confusing when trailers or other movie versions have the same name as the movie version to be shown. The Digital Cinema Naming Convention was created to address this problem. The Digital Cinema Naming Convention is described at DigitalCinemaNamingConvention.com.

Digital cinema security, per the DCI specification, relies on a series of NIST standards that, due to their complexity and nature, are perpetually in amendment. NIST documents that affect digital cinema are listed below.

NIST Miscellaneous and Special Publications

SP 800-131 DRAFT Recommendation for the Transitioning of Cryptographic Algorithms and Key Lengths (June 2010)
Received Comments on SP 800-131 (scroll to end for comment from DCI)
SP 800-107 Recommendation for Applications Using Approved Hash Algorithms (February 2009)
SP 800-57 Recommendation for Key Mangement Part 1 (March 2007)
SP 800-57 Recommendation for Key Mangement Part 2 (November 2002)
SP 800-57 Recommendation for Key Mangement Part 3 (December 2009)
FIPS-180-2 Secure Hash Standard (SHS) (August 2002)
FIPS-180-3 Secure Hash Standard (SHS) (October 2008)
FIPS-186-2 Digital Signature Standard (January 2000)
FIPS-186-3 Digital Signature Standard (June 2009)

FIPS 140-2

FIPS 140-2 Security Requirements for Cryptographic Modules
FIPS 140-2 Annex A (January 27, 2010)
FIPS 140-2 Annex A (December 18, 2007)
FIPS 140-2 Annex A (May 19, 2005)
FIPS 140-2 Annex B (June 14, 2007)
FIPS 140-2 Annex C (July 21, 2009)
FIPS 140-2 Annex D (October 8, 2009)
Implementation Guide for FIPS 140-2 (January 27, 2010)

FIPS 140-3

FIPS-140-3 DRAFT Security Requirements for Cryptographic Modules (Revised Draft December 11, 2009)