SMPTE ST 430-9-2008 D-Cinema Operations Key Delivery Bundle.pdf

《SMPTE ST 430-9-2008 D-Cinema Operations Key Delivery Bundle.pdf》由会员分享，可在线阅读，更多相关《SMPTE ST 430-9-2008 D-Cinema Operations Key Delivery Bundle.pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 Copyright 2008 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 595 W. Hartsdale Ave., White Plains, NY 10607 (914) 761-1100 Approved February 1, 2008 Table of Contents Page Foreword . 2 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Overview (Informative). 4 5 Bundle File F

2、ormat 4 6 Basic KDMb Elements and D-Cinema Relationships . 4 6.1 CATALOG File 4 6.2 CONTENT Directory . 5 7 Catalog Element 6 7.1 Id . 6 7.2 AnnotationText (Optional) . 6 7.3 Creator (Optional) . 6 7.4 KDMFileList. 6 8 KDMFile Element 7 8.1 CPLId 7 8.2 FilePath . 7 8.3 Recipient . 8 9 XML Schema. 9

3、10 Bundle Catalog File Example (Informative) . 10 11 XML Diagram Legend (Informative). 12 11.1 Element Symbols 12 11.2 Model Symbols (“Compositors“) . 13 11.3 Types 13 11.4 Model Groups and References. 14 Annex A Bibliography (Informative) 15 Table of Figures Figure 1 KDM Bundle Structure Overview 4

4、 Figure 2 Catalog Relationships. 5 Figure 3 CatalogType Structure 6 Figure 4 KDMFileType Structure 7 Figure 5 KDM Recipient Structure 8 Page 1 of 15 pages SMPTE 430-9-2008SMPTE STANDARD D-Cinema Operations Key Delivery Bundle SMPTE 430-9-2008 Page 2 of 15 pages Foreword SMPTE (the Society of Motion

5、Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices and

6、 Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted

7、 in accordance with the rules given in Part XIII of its Administrative Practices. SMPTE Standard 430-9 was prepared by Technology Committee DC28. SMPTE 430-9-2008 Page 3 of 15 pages 1 Scope This document specifies the Key Delivery Message bundle (KDMb). The KDMb is designed to deliver a set of Key D

8、elivery Messages KDM from a D-Cinema content processing center to a consumer or redistributors of KDM elements (e.g., from post production to distribution, or from distribution to exhibition). The KDMb can represent an entire theatre, circuit or other grouping of recipients. The KDMb is a compressed

9、 archive that contains a mapping file and a directory containing a collection of one or more KDM files. The mapping file defines a relationship between a Composition Playlist CPL, a Recipient and a KDM. The mapping file allows for a fast look-up of a KDM elements for CPL or Recipient. The intent of

10、the KDMb is to distribute a set of KDM elements in a single compressed container for improved distribution efficiencies. 2 Conformance Notation Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: “shall“, “should“, or “ma

11、y“. Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords. All text in this document is, by default, normative, except:

12、the Introduction, any section explicitly labeled as “Informative“ or individual paragraphs that start with “Note:” The keywords “shall“ and “shall not“ indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted. The keywords, “should“ a

13、nd “should not“ indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is d

14、eprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision that is not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indica

15、tes “reserved” and in addition indicates that the provision will never be defined in the future. A conformant implementation according to this document is one that includes all mandatory provisions (“shall“) and, if implemented, all recommended provisions (“should“) as described. A conformant implem

16、entation need not implement optional provisions (“may“) and need not implement them as described. 3 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were v

17、alid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. World Wide Web Consortium (W3C) (2004, February 4). Extensible Markup Language (XML) 1.0 (

18、Third Edition) World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edition) World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 2: Datatypes (Second Edition) Internet Engineering Task Force (IETF) (November 1996) RFC1738 - Uniform Resource Locato

19、rs (URL) SMPTE 430-9-2008 Page 4 of 15 pages Internet Engineering Task Force (IETF) (1996, November). RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax Internet Engineering Task Force (IETF) (2005, July). RFC 4122 A Universally Unique Identifier (UUID) URN Namespace.7 SMPTE 429-7-2006, D-C

20、inema Packaging Composition Playlist SMPTE 429-8-2007, D-Cinema Packaging Packing List SMPTE 430-1-2006, D-Cinema Operations Key Delivery Message IEEE Std 1003.1-2004, Standard for Information Technology Portable Operating System Interface (POSIX) 4 Overview (Informative) The Bundle is designed to d

21、eliver a collection of Key Delivery Messages KDM from a D-Cinema content processing center to a consumer or redistributors of KDM elements (e.g., from post production to distribution, or from distribution to exhibition). The Bundle can contain KDMs for an entire theatre, circuit or other grouping of

22、 recipients. The Bundle is a single archive file that contains a Catalog file and a collection of one or more KDM files in a hierarchical directory structure. The Catalog file defines a relationship between a Composition Playlist CPL, a Recipient and a KDM contained in the Bundle. The Catalog file a

23、llows for a fast look-up of KDM associated with a CPL or Recipient. The intent of the Bundle is to distribute a set of KDM files in a single container for improved distribution efficiencies. It is recommended that the reader become familiar with the Key Delivery Message KDM and Composition Playlist

24、CPL specifications in order to fully understand the concepts expressed within this document. 5 Bundle File Format The Bundle file format shall follow the ustar Interchange Format defined in IEEE Std 1003.1(POSIX). 6 Basic KDMb Elements and D-Cinema Relationships The Bundle shall contain at its top-l

25、evel a single text file named CATALOG and a single directory named CONTENT that contains one or more KDM files. Other top-level files and directories shall be ignored. Figure 1 KDM Bundle Structure Overview 6.1 CATALOG File The CATALOG file is encoded using the Extensible Markup Language (XML) XML 1

26、.0. It shall contain a single Catalog element, as defined in the following sections. SMPTE 430-9-2008 Page 5 of 15 pages The Catalog element is specified using XML Schema XML Schema Part 1: Structures and XML Schema Part 2: Datatypes. This specification shall be associated with a unique XML namespac

27、e name Namespaces in XML. The namespace name shall be the string value “http:/www.smpte-ra.org/schemas/429-10/2008/KDMB”. Figure 2 Catalog Relationships 6.2 CONTENT Directory The CONTENT directory shall contain one or more files. Each file shall contain a single Key Delivery Message, as specified in

28、 KDM. Any file name permitted by the ustar Interchange Format is allowed. SMPTE 430-9-2008 Page 6 of 15 pages 7 Catalog Element Figure 3 CatalogType Structure 7.1 Id Id shall be encoded as a urn:uuid per RFC 4122. The Id element uniquely identifies the Catalog for asset management purposes. 7.2 Anno

29、tationText optional The Annotation Text element shall be encoded as a dcmlTypes:UserTextType. The Annotation Text element shall be a free-form, human-readable annotation describing the Catalog. It is meant strictly as a display hint to the user. 7.3 Creator optional The Creator element shall be enco

30、ded as a dcmlTypes:UserTextType. The Creator element shall be a free-form, human-readable annotation that shall identify the application used to create the Show Playlist. It is meant strictly for display to the user. 7.4 KDMFileList The KDMFileList element contains a list of KDMFile elements. Each K

31、DMFile element shall correspond to a single file contained in the CONTENT directory. The structure of the KDMFile element is described in the following section. SMPTE 430-9-2008 Page 7 of 15 pages 8 KDMFile Element Figure 4 KDMFileType Structure The KDMFile element is used to represent a single KDM

32、file contained in the CONTENT directory. It contains the following elements. 8.1 CPLId CPLId shall be encoded as a urn:uuid per RFC 4122. The CPLId element shall be a copy of the Id of the Composition Playlist associated with the KDM contained in the associated KDM file. 8.2 FilePath FilePath shall

33、be encoded as a PathTextType element. The FilePath element shall contain the filename of the associated KDM file, relative to the root of the CONTENT directory. The minimum length of the path shall be one character and the maximum length shall not exceed 99 characters. 8.2.1 Archive File Attributes

34、All of the archive files must have the following attributes: 1. All archive files shall be regular files or directories (no symbolic links or device files). 2. All archive files shall have permission mode (octal) 0444 (read- only). 3. All archive directories shall have permission mode (octal) 0555 (

35、read-only, searchable). 4. All archive files shall have relative pathnames (no absolute paths). 5. All archive files shall have user and group id of 0 (zero). 6. All archive files shall have a text user id and text group id of “root”. 7. All archive files shall be case-sensitive, however all names s

36、hall be unique without regard to case. SMPTE 430-9-2008 Page 8 of 15 pages 8.2.2 PathTextType PathTextType constrains the path text to have the following attributes: 1. File and directory names shall contain a-z, A-Z, 0-9, “_” (underscore), “-” (dash), and “.” (dot) 8- bit ASCII characters only. 2.

37、File and directory names shall not contain whitespace characters. 3. The path separator shall be a “/” (forward slash) character. 4. File and directory names shall begin with an alphanumeric character (a-z, A-Z, 0-9). 8.3 Recipient The Recipient field shall identify the intended certificate/subject

38、of the associated KDM. The public key identified in this certificate is used to encrypt the keys found in the AuthenticatedPrivate portion of the KDM message. An X.509 certificate is identified by the name of the Certificate Authority (CA) that issued it, called IssuerName, and the unique serial num

39、ber assigned by the CA, called SerialNumber. To aid in routing of KDMs, the X.509 SubjectName that is found in the certificate shall also be placed in the Recipient element. Figure 5 KDM Recipient Structure SMPTE 430-9-2008 Page 9 of 15 pages 9 XML Schema The XML Schema document presented in this se

40、ction normatively defines the structure of the Catalog element. While this schema is intended to faithfully represent the structure presented in the normative prose portions of this document, conflicts in definition may occur. In the event of such a conflict, the normative prose shall be the authori

41、tative expression of the standard. SMPTE 430-9-2008 Page 10 of 15 pages 10 Bundle Catalog File Example (Informative) urn:uuid:00000000-0000-0000-0000-000000000000 Example KDM Bundle DCIP urn:uuid:1c8ea7cb-92cd-4343-88c3-475047590a0b KDM_0c8ea7cb-92cd-4343-88c3-475047590a0b.xml dnQualifier=NE0=,CN=CO

42、M,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1c8ea7cb-92cd-4343-88c3-475047590a0c KDM_0c8ea7cb-92cd-4343-88c3-475047590a0c.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU

43、=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1c8ea7cb-92cd-4343-88c3-475047590a0d KDM_0c8ea7cb-92cd-4343-88c3-475047590a0d.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-1

44、7T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1d8ea7cb-92cd-4343-88c3-475047590a0b Feature-1/KDM_1d8ea7cb-92cd-4343-88c3-475047590a0b.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM SMPTE 430-9-2008 Page 11 of 15 pages 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T0

45、9:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1d8ea7cb-92cd-4343-88c3-475047590a0c Feature-1/KDM_1d8ea7cb-92cd-4343-88c3-475047590a0c.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z 2010-1

46、2-17T09:30:47.0Z urn:uuid:1d8ea7cb-92cd-4343-88c3-475047590a0d dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1e8ea7cb-92cd-4343-88c3-475047590a0b Feature-2/KDM_1e8ea7cb-92cd-4343

47、-88c3-475047590a0b.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1e8ea7cb-92cd-4343-88c3-475047590a0c Feature-2/KDM_1e8ea7cb-92cd-4343-88c3-475047590a0c.xml dnQualifier=NE0=,

48、CN=COM,OU=INC,O=COM 0123456789 dnQualifier=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM 2001-12-17T09:30:47.0Z 2010-12-17T09:30:47.0Z urn:uuid:1e8ea7cb-92cd-4343-88c3-475047590a0d Feature-2/KDM_1e8ea7cb-92cd-4343-88c3-475047590a0d.xml dnQualifier=NE0=,CN=COM,OU=INC,O=COM 0123456789 dnQualifi

49、er=ZH/ SMPTE,OU=DC.DCIP.COM,O=DC20070301.SMPTE.DCIP.COM SMPTE 430-9-2008 Page 12 of 15 pages 11 XML Diagram Legend (Informative) The following provides a legend for notation used in diagrams depicting XML structures. 11.1 Element Symbols In the schema design diagrams presented above in this document, only the elements are drawn. Attributes are not visible. The cardinality of the element (01, 1 exactly, 0n, 1n) is indicated by the border of the elements. Opt