Network Working Group T. Edwards Internet-Draft PBS Expires: August 4, 2007 January 31, 2007 A Uniform Resource Name (URN) Namespace for the Society of Motion Picture and Television Engineers (SMPTE) draft-edwards-urn-smpte-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 4, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document describes a Uniform Resource Name (URN) namespace for the Society of Motion Picture and Television Engineers (SMPTE) for naming persistent resources that SMPTE produces or manages. A subnamespace for Universal Labels is specifically described. Edwards Expires August 4, 2007 [Page 1]
Internet-Draft SMPTE URN Definition January 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. URN Namespace Definition Template . . . . . . . . . . . . . . 3 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Namespace Considerations and Community Considerations . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. SMPTE Registration Authority (Informative) . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 10 Edwards Expires August 4, 2007 [Page 2]
Internet-Draft SMPTE URN Definition January 2007 1. Introduction SMPTE (the Society of Motion 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. SMPTE's Engineering Documents, including Standards, Recommended Practices and Engineering Guidelines, are prepared by SMPTE's 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. Also, the SMPTE Registration Authority maintains a registry of Universal Labels (ULs) used in identifying the type and encoding of data within data streams associated with audio-visual material. SMPTE would like to assign unique, permanent, and location- independent names using URNs for resources that SMPTE produces or manages. This namespace specification is for a formal namespace. 2. URN Namespace Definition Template The following template is provided in accordance with [RFC3406]. Namespace ID: smpte Registration Information: Version: 1 Date: 2006 12 8 Declared registrant of the namespace: Organization: Society of Motion Picture and Television Engineers Contact: Director of Engineering Address: 3 Barker Avenue - 5th Floor Edwards Expires August 4, 2007 [Page 3]
Internet-Draft SMPTE URN Definition January 2007 White Plains, NY 10601 USA Phone: +1 (914) 761-1100 Email: standards@smpte.org Declaration of structure: The Namespace Specific String (NSS) of all URNs that use the "smpte" NID shall be conformant to the URN syntax requirements defined in [RFC2141]. URNs for the "urn:smpte" namespace shall follow the structure defined in [SMPTExxxx]. SMPTE (or it successor) may add additional subnamespaces in the future. Any system which deals with URNs for the "urn:smpte" namespace should be written with the awareness that this could occur at any time. For informative purposes, the identifier structure described using ABNF (according to [RFC4234]) is as follows: ;start ABNF notation URN = "urn:" NID NSS NID = "smpte:" NSS = UL-NSS / other-NSS UL-NSS = "ul:" UL UL = QUADBYTE *(DOT QUADBYTE) DOT = %x2E ; period QUADBYTE = 4BYTE BYTE = 2HEXDIG other-NSS = 1*(DIGIT / ALPHA / "-"/":") ; other-NSS which conforms with [RFC2141] for future expansion Edwards Expires August 4, 2007 [Page 4]
Internet-Draft SMPTE URN Definition January 2007 ;end ABNF notation Relevant ancillary documentation: The structure for URNs in the "urn:smpte" namespace are defined in [SMPTExxxx]. The values of ULs in the "urn:smpte:ul" subnamespace shall be constrained as defined in [SMPTE298M]. Details regarding the use of ULs as keys in key-length-value (KLV) coding including how to determine in which SMPTE registry a SMPTE-administered UL may be found are described in [SMPTE336M]. Identifier uniqueness considerations: The rules for assignment of SMPTE-administered ULs requires that each UL be unique to the UL space and that it cannot be reassigned or reused. It should be noted that [SMPTE298M] states that "A universal label shall be an 'object identifier' as specified by ISO/IEC 8824-1," although the SMPTE Universal Label representation is a specialized one that carries additional semantics over the OID representation of URN OID ([RFC3001]). SMPTE will work to ensure that all current and future "urn:smpte" subnamespaces contain unique identifiers. Identifier persistence considerations: SMPTE-administered ULs may occasionally be deleted through SMPTE procedures. Regardless, even after a UL has been deleted, it will not be reused. Revisions to ULs will result in the creation of a new UL, and the deletion of the old one. The persistence of URNs in future "urn:smpte" subnamespaces will be defined by SMPTE Standards. Process of identifier assignment: Assignment of URNs in the SMPTE NID is limited to SMPTE and those authorities that are specifically designated by SMPTE. SMPTE may designate portions of its namespace for assignment by other parties. Edwards Expires August 4, 2007 [Page 5]
Internet-Draft SMPTE URN Definition January 2007 Due process is followed by committees in the development of SMPTE documents. Some types of Universal Label registrations, and other registrations may require a fee to be paid to SMPTE. All classes of SMPTE-administered ULs require for registration the name and address of the applicant. Some classes of labels also require the submission of supporting technical documentation for the label and may require a due process evaluation through the SMPTE Engineering Committee process. Process for identifier resolution: SMPTE-administered ULs are resolved through publications of the SMPTE Registration Authority. Currently, publication of SMPTE- administered ULs are made through a Metadata Dictionary as specified in [RP210] and through the SMPTE Labels Registry as specified in [RP224], both of which are currently available online at http://www.smpte-ra.org/mdd/. SMPTE expects to develop and maintain "URN catalogs" that map all future assigned URNs in the "urn:smpte" namespace to Uniform Resource Locators (URLs) to enable Web-based resolution of named resources. Rules for Lexical Equivalence: Lexical equivalence of URNs in the "urn:smpte:ul" subnamespace is achieved by a exact string match which is case-insensitive for alphabetical characters. Conformance with URN Syntax: No special considerations beyond the syntax herein described. Validation mechanism: None. Scope: Global. 3. Examples Currently only a "urn:smpte:ul" subnamespace is defined. This is the subnamespace for SMPTE Universal Labels [SMPTE298M]. SMPTE may add additional subnamespaces in the future. The following examples are not guaranteed to be real, and are Edwards Expires August 4, 2007 [Page 6]
Internet-Draft SMPTE URN Definition January 2007 provided for illustrative purposes only. urn:smpte:ul:060E2B34.04010103.04010202.01011100 urn:smpte:newnss:future-urn-2105 4. Security Considerations There are no additional security considerations other than those normally associated with the use and resolution of URNs in general. 5. Namespace Considerations and Community Considerations SMPTE is an internationally-recognized standards developing organization. As part of this effort, SMPTE also registers items such as Universal Labels through the SMPTE Registration Authority. The SMPTE namespace provides a uniform, unique, and effective way to communicate resource names for these items, which can be used by the motion imaging industry community. This namespace is also intended to be a useful mechanism to provide both human and automated access to these resources through online systems. The individual URNs in the namespace shall be assigned through the process of development of documents by SMPTE, through definition by SMPTE standards, or through the registration of Universal Labels or other items by the SMPTE Registration Authority. 6. IANA Considerations This document defines a URN NID registration that is to be entered into the IANA registry of URN NIDs. It specifically requests the NID, "smpte". 7. SMPTE Registration Authority (Informative) The URL of the SMPTE Registration Authority is http://www.smpte-ra.org. 8. References Edwards Expires August 4, 2007 [Page 7]
Internet-Draft SMPTE URN Definition January 2007 8.1. Normative References [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [SMPTExxxx] Society of Motion Picture and Television Engineers, "Uniform Resource Names for SMPTE Resources", SMPTE xxxx, <http://www.smpte.org> (to be published). 8.2. Informative References [ISO.8824-1:1995] International Organization for Standardization, "Information Processing - Open System Interconnection - Specification of Abstract Syntax Notation One (ASN.1)", ISO Standard 8824-1:1995, 1995. [RFC3001] Mealling, M., "A URN Namespace of Object Identifiers", RFC 3001, November 2000. [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. [RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005. [RP210] Society of Motion Picture and Television Engineers, "Metadata Dictionary Registry of Metadata Element Descriptions", SMPTE RP210, <http://www.smpte.org>. [RP224] Society of Motion Picture and Television Engineers, "Registry of SMPTE Universal Labels", SMPTE RP224, <http://www.smpte.org>. [SMPTE298M] Society of Motion Picture and Television Engineers, "Universal Labels for Unique Identification of Digital Data", ANSI / SMPTE 298M-1997, <http://www.smpte.org>. [SMPTE336M] Society of Motion Picture and Television Engineers, "Data Encoding Protocol using Key-Length-Value", SMPTE 336M- 2001, <http://www.smpte.org>. Edwards Expires August 4, 2007 [Page 8]
Internet-Draft SMPTE URN Definition January 2007 Author's Address Thomas G. Edwards PBS 6453 Stephenson Way Alexandria, VA 22312 US Phone: +1 703 739 5000 Email: tedwards@pbs.org URI: http://www.pbs.org Edwards Expires August 4, 2007 [Page 9]
Internet-Draft SMPTE URN Definition January 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Edwards Expires August 4, 2007 [Page 10]
