Network Working Group Gary Ellison Internet-Draft Intertrust Intended status: Informational June 28, 2007 Expires: December 29, 2007 A Uniform Resource Name (URN) Namespace for the Marlin Development Community L.L.C. draft-ellison-urn-marlin-02 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. This document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English. 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. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document describes a Uniform Resource Name (URN) namespace that will identify various objects of Marlin system implementations to enable interoperability and content portability. Table of Contents 1. Introduction ....................................................2 2. URN Specification for the "marlin" NID ..........................2 3. IANA Considerations .............................................4 4. Community Considerations ........................................4 5. Security Considerations .........................................4 6. References ......................................................5 Ellison Informational [Page 1] INTERNET-DRAFT The Marlin URN Namespace June 2007 1. Introduction This document proposes the "marlin" namespace, which consists of the specifications, protocol bindings, XML schema and service definitions developed by the Marlin Development Community L.L.C. One fundamental component of this architecture is its use of XML [5], and specifically, XML Schema [7] and Namespaces [6]. These components require identifiers that will live far beyond the lifetime of the organization that produced them. As such, a URN namespace for those components that adheres to the assumptions and policies of the Marlin specifications is required. This namespace specification is for a formal namespace. 2. URN Specification for the "marlin" NID Namespace ID: The NID "marlin" is requested. Registration Information: Registration Version Number: 1 Registration Date: 2007-6-28 Declared registrant of the namespace: Name: Gary Ellison Affiliation: Marlin Development Community L.L.C. Address: 415-112 North Mary Ave., Suite #383 Sunnyvale, CA 94085 USA Phone: +1 (408) 616-1600 Email: editor@marlin-community.com Declaration of structure: The Namespace Specific Strings (NSS) of all URNs assigned by Marlin [4] will conform to the syntax defined in section 2.2 of RFC 2141 [1]. In addition, all Marlin 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 RFC 2396 [2] 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. Ellison Informational [Page 2] INTERNET-DRAFT The Marlin URN Namespace June 2007 This syntax convention is captured in the following normative ABNF [3] rules for Marlin NSSs: ALPHA = %x41-5A / %x61-7A ; A-Z / a-z DIGIT = %x30-39 ; 0-9 HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" Marlin-NSS = 1*(subStChar) 0*(":" 1*(subStChar)) subStChar = trans / "%" HEXDIG HEXDIG trans = ALPHA / DIGIT / other / reserved other = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved = "%" / "/" / "?" / "#" The exclusion of the colon from the list of "other" characters means that the colon can only occur as a delimiter between string tokens. Note that this ABNF rule set guarantees that any valid Marlin NSS is also a valid RFC 2141 [1] NSS. For example: urn:marlin:core:1-0:schemas urn:marlin:drmservices Relevant ancillary documentation: The structure for URNs in the "urn:marlin" namespace are defined in [4]. Identifier uniqueness considerations: Identifiers are assigned by the techical committees within the Marlin Development Community L.L.C. In the process of publishing a specification all newly minted names are checked against the record of previously assigned names. 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. Process of identifier assignment: Names are assigned by the Marlin Development Community L.L.C. standards publication process. Process of identifier resolution: At this time no resolution mechanism is specified. Ellison Informational [Page 3] INTERNET-DRAFT The Marlin URN Namespace June 2007 Rules for Lexical Equivalence: Lexical equivalence of two Marlin namespace specific strings (NSSs) is defined as an exact, case sensitive string match. The Marlin Development Community L.L.C. will assign names of immediately subordinate naming authorities in a case-insensitive fashion, so that there will not be two Marlin-subordinate naming authorities whose names differ only in case. Conformance with URN Syntax: There are no additional characters reserved. Validation mechanism: None other than verifying with the correct Marlin specifications. Scope: Global 3. IANA Considerations This document includes a URN Namespace registration that has been entered into the IANA registry for URN NIDs. 4. Community Considerations While there is no resolution mechanism for this namespace, the names themselves are used in public implementations of the Marlin specifications. There are circumstances where objects from the Marlin system will become exposed to the general Internet. In these cases, the use of the Marlin namespace will provide general interoperability benefits to the Internet at large. Additionally, there may be subcomponents of the Marlin 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-Marlin based, systems. 5. Security Considerations Since there is no defined resolution mechanism for Marlin 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. Ellison Informational [Page 4] INTERNET-DRAFT The Marlin URN Namespace June 2007 6. References 6.1. Normative References [1] Moats, R., "URN Syntax", RFC 2141, May 1997. [2] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 3986, January 2005. [3] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005. [4] Marlin Developer Community L.L.C., "Marlin Core System Specification", Septermber 2006, . 6.2. Informative References [5] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, . [6] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, . [7] Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, . Ellison Informational [Page 5] INTERNET-DRAFT The Marlin URN Namespace June 2007 Author's Address Gary Ellison Intertrust, Inc. 955 Stewart Drive Sunnyvale, CA 94085 USA Phone: +1 408 616 1625 EMail: gfe@intertrust.com URI: http://www.intertrust.com Ellison Informational [Page 6] INTERNET-DRAFT The Marlin URN Namespace June 2007 Full Copyright Notice 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. Ellison Informational [Page 7] INTERNET-DRAFT The Marlin URN Namespace June 2007 Expires: December 29, 2007 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. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Ellison Informational [Page 7]