Background Documents
Updated July 7, 2011
FLM information http://flm.foxpico.com/ username: isdcf password: isdcf
Hard Disc Drive formats (updated June 2010) Completion!
This is the new ISDCF recommendation for Digital Cinema systems to support hard drives and other media with both Interop and SMPTE Digital Cinema Packages. It provides a recommendation to allow multiple asset maps in separate directories on the same media. Click HERE for details.
FLM-x Discussion (updated May 2010)
A discussion list has been created for the Mike Radford / Fox proposed FLM-x coordination. Join the discussion: http://lists.isdcf.com/listinfo.cgi/flm-x-isdcf.com
Other Stuff:
Department of Justice registry on Disability (October 11, 2010 update)
The Department of Justice (DOJ) has posted documents about "Nondiscrimination on the Basis of Disability; Movie Captioning and Video Description.” The original document is http://edocket.access.gpo.gov/2010/pdf/2010-18337.pdf an excerpted version with relevant parts are posted Request for Comments: Dept of Justice: Movie Captioning and Video Description these include questions from interested parties (much easier to read).
DCI Compliance Update (July 13, 2010 update)
There are now many projector products that have passed the DCI compliance test plan. These are posted to the DCI website: http://www.dcimovies.com/compliance/
NIST/FIPS-140-2 Update (June 21, 2010 update)
There has been considerable conversation at ISDCF over the NIST update to FIPS-140. The question included the DCI-Specification, the Compliance Test Plan, and SMPTE documents referring to a soon-to-not-exist (or recently changed) standard. Posted at the NIST site are draft NIST publications (go HERE) and in particular are public comments (go HERE for all comments) of most interest are DCI comments that were submitted - go HERE for the DCI comments.
Content ID, Facility ID
Coming soon! Well, maybe not very soon.
3D Screen Luminance Measurement (updated June 2010)
How to measure the screen brightness of a 3D screen came up in a discussion in the January 2010 time frame. A discussion thread has been underway with no conclusions, but some good input. Peter Wilson put the thread together into a .pdf document. It’s posted HERE.
US 9th Circuit Court Ruling on Closed Captions (updated May 2010) Final - until additional actions
In a lawsuit brought against Harkins Theaters in Arizona an opinion is offered for the requirements of Closed Caption in Theatrical Exhibition. HERE is the ruling.
Forensic Tracking (updated November 2007) Informational only
Go HERE for the document.
Upgrade Schedule To Meet SMPTE Distribution Standards (SMPTE DCP) Including Accessibility Features
The transition to SMPTE DCP is targeted for April 2011. The document below is the most recent work that describes the timeline for implementation of SMPTE DCP, including accessibility features. The latest Document is HERE.
KDM Distribution and the Cinema Communication Message - (early drafts) In Process
The documents below capture early thinking towards managing KDM distribution, including the use of the Cinema Communication Message, or CCM. The CCM 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.
KDM Distribution Portal (draft v2).pdf
Facility Identifiers (In Process)
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
Updated Link: http://mkpe.com/digital_cinema/isdcf/identifier/2010-11-11%20Cinema%20Facility%20Identifier.pdf
Key Delivery Message (KDM) Naming Convention (In Process)
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.
NIST Security Standards (Subject to change)
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-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)
All these documents are to be used at your own risk, strictly voluntary, not to be used for implementing products, no warranty expressed or implied. We provide these for convenience only.
Contact: info@isdcf.com to offer suggestions/ corrections. USE AT YOUR OWN RISK