Network Working Group P. Davis, Ed. Internet-Draft Neustar, Inc. Intended status: Informational Sep 02, 2011 Expires: March 5, 2012 A URN Namespace for the Digital Entertainment Content Ecosystem draft-davis-urn-dece-00 Abstract This document describes a URN (Uniform Resource Name) namespace that is to be employed by the Digital Entertainment Content Ecosystem (DECE), LLC. for naming persistent resources published by DECE, including XMLSchemas, resource definitions, terms, and other structures. Management activities for these and other resource types, as well as their identifiers are provided by the DECE, LLC. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on March 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as Davis Expires March 5, 2012 [Page 1] Internet-Draft DECE URN Sep 2011 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. URN Namespace Definition Template . . . . . . . . . . . . . . . 3 2.1. Relevant Ancillary Documentation . . . . . . . . . . . . . 4 2.2. Identifier Uniqueness Considerations . . . . . . . . . . . 4 2.3. Identifier Persistence Considerations . . . . . . . . . . . 4 2.4. Process of identifier assignment . . . . . . . . . . . . . 5 2.5. Process of identifier resolution . . . . . . . . . . . . . 5 2.6. Rules for Lexical Equivalence . . . . . . . . . . . . . . . 5 2.7. Conformance with URN Syntax . . . . . . . . . . . . . . . . 5 2.8. Validation mechanism . . . . . . . . . . . . . . . . . . . 5 2.9. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. Namespace Considerations . . . . . . . . . . . . . . . . . . . 6 6. Community Considerations . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 Davis Expires March 5, 2012 [Page 2] Internet-Draft DECE URN Sep 2011 1. Introduction The Digital Entertainment Content Ecosystem (DECE) produces specifications, working drafts, technical resolutions, schemas, stylesheets, etc. DECE wishes to provide global, distributed, persistent, location- independent names for these resources. The Extensible Markup Language (XML) requires that all resources provide a system identifier, which must be a URI, in addition to an optional public identifier (which provides an alternate mechanism for constructing identifiers) and many evolving specifications require authors to identify documents by URI alone (XML Namespaces, XML Schema, XSLT, etc.). DECE would like to assign URNs to some resources in order to retain unique, permanent location-independent names for them. This namespace specification is for a formal namespace. 2. URN Namespace Definition Template The following template is provided in accordance with [RFC3406]. NamespaceID: dece Registration Information: Registration Version Number: 1 Registration Date: YYYY-MM-DD [RFC Editor, please replace with the date of approval of this document for publication as an RFC] Declared Registrant of the Namespace: Registering Organization Name: Digital Entertainment Content Ecosystem, LLC (DECE) Address: 1807 Santa Rita Road Suite D235 Pleasanton, CA 94566 Davis Expires March 5, 2012 [Page 3] Internet-Draft DECE URN Sep 2011 Designated Contact: Role: DECE Technical Administrator Email: technicalinquiries@decellc.com The Namespace Specific Strings (NSS) of all URNs assigned by DECE will conform to the syntax defined in section 2.2 of [RFC2141]. In addition, all DECE URN NSSs will consist of a left-to-right series of tokens delimited by colons. The left-to- right sequence of colon- delimited tokens corresponds to descending nodes in a tree. To the right of the lowest naming authority node there may be zero, one or more levels of hierarchical (although not in the [RFC2396] sense of 'hierarchy') naming nodes terminating in a rightmost leaf node. See the section entitled "Identifier assignment" below for more on the semantics of NSSs. This syntax convention is captured in the following normative Backus-Naur Form (BNF) rules for DECE NSSs: ::= "urn:dece:" For example: urn:dece:apid:isan:000000018947000000000000:a203 urn:dece:type:policy:TermsOfUse 2.1. Relevant Ancillary Documentation Systems Specification [DSystem] Requests for copies of this publication may be made via http://www.uvvu.com/contact-us.php Version 1.0 DECE, LLC. 2.2. Identifier Uniqueness Considerations Identifiers are assigned by the DECE Technical Working Group. In the process of identifier assignment, the registration authority confirms assignment against the record of previously assigned names. 2.3. Identifier Persistence Considerations The assignment process guarantees that names are not reassigned and that the binding between the name and its resource is permanent, regardless of any standards or organizational changes. Davis Expires March 5, 2012 [Page 4] Internet-Draft DECE URN Sep 2011 2.4. Process of identifier assignment Names are assigned by the DECE Technical Working Group. 2.5. Process of identifier resolution At this time no resolution mechanism is specified. 2.6. Rules for Lexical Equivalence Lexical equivalence of two DECE namespace specific strings (NSSs) is defined as an exact, case-insensitive string match. 2.7. Conformance with URN Syntax No special considerations. The syntax is fully conformant with [RFC2141]. 2.8. Validation mechanism None. 2.9. Scope The scope shall be global. 3. Formal Syntax The following syntax specification uses the augmented Backus-Naur Form (BNF) and elements defined in the URN Syntax [RFC2141]. This syntax here is derived from the syntax definition in [DSystem]. ::= "urn:dece:"":"":" (* Types are explicitly defined in [DSystem], omitted here for brevity *) ::= 1* ::= 1* ::= ":" ::= 1* ::= 1* Davis Expires March 5, 2012 [Page 5] Internet-Draft DECE URN Sep 2011 4. Security Considerations Since there is no defined resolution mechanism for DECE URNs it is difficult to authenticate the fact that a given namespace actually adheres to the standard, thus applications should be careful to not take some unverified sources assertion that what it is sending adheres to what the actual URN is assigned to. 5. Namespace Considerations DECE-NSS identifiers are reserved for use in identifying system entities, resources, namespaces and works, among others, for the incorporation in DECE client processing and protocol messages 6. Community Considerations While there is no resolution mechanism for this namespace, the names themselves are exposed to consumers of DECE defined resource within this namespace. There are circumstances where objects from the DECE ecosystem will become exposed to the general Internet. In these cases, the use of the DECE namespace will provide general interoperability benefits to the Internet at large. Additionally, there may be subcomponents of the DECE specifications that may be adopted by other standards, in which case the URNs used to identify those components and specifications can be easily used to enhance other, non-DECE based, systems. 7. IANA Considerations This document includes a URN Namespace registration that is to be entered into the IANA registry for URN NIDs. 8. References 8.1. Normative References [DSystem] Gerson, D., "System Specification". [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Davis Expires March 5, 2012 [Page 6] Internet-Draft DECE URN Sep 2011 Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. 8.2. Informative References [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. Author's Address P. Davis (editor) Neustar, Inc. Email: peter.davis@neustar.biz Davis Expires March 5, 2012 [Page 7]