Internet DRAFT - draft-carey-urn-coral
draft-carey-urn-coral
INTERNET-DRAFT Knox Carey
draft-carey-urn-coral-00.txt Intertrust
Spetember 2005
A Uniform Resource Name (URN) Namespace for
the Coral Consortium Corporation
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved.
IPR Statement
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.
Abstract
This document describes a Uniform Resource Name (URN) namespace
that will identify various objects in Coral system
implementations to facilitate interoperability of digital
rights management systems.
1. Introduction
This document proposes the "coral" namespace, which consists of
the specifications, protocol bindings, XML schema and service
definitions developed by the Coral Consortium Corporation.
One fundamental component of this architecture is its use of XML [4],
and specifically, XML Schema [6] and Namespaces [5]. 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
Coral specifications is required.
This namespace specification is for a formal namespace.
2. IANA URN Specification Template
Namespace ID:
"coral" requested.
Registration Information:
Registration Version Number: 1
Registration Date: 2005-09-30
Declared registrant of the namespace:
Name: Knox Carey
Affiliation: Intertrust Technologies Corporation
Address: 955 Stewart Drive
Sunnyvale, CA 94085 USA
Phone: +1 (408) 616-1666
Email: info@coral-interop.org
Declaration of structure:
The Namespace Specific Strings (NSS) of all URNs assigned by
Coral will conform to the syntax defined in section 2.2 of RFC
2141 [1]. In addition, all Coral 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.
This syntax convention is captured in the following normative ABNF
[3] rules for Coral NSSs:
Coral-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
Coral NSS is also a valid RFC 2141 NSS.
For example:
urn:coral:core:2-1:roles
urn:coral:demo:core:2-1:roles:role-issuer
Relevant ancillary documentation:
None.
Identifier uniqueness considerations:
Identifiers are assigned by the techical committees within the
Coral Consortium Corporation. 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 Coral Consortium Corporation
standards publication process.
Process of identifier resolution:
At this time no resolution mechanism is specified.
Rules for Lexical Equivalence:
Lexical equivalence of two Coral namespace specific strings
(NSSs) is defined as an exact, case-sensitive string match. The
Coral Consortium Corporation will assign names of immediately
subordinate naming authorities in a case-insensitive fashion, so
that there will not be two Coral-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 Coral 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 Coral
specifications. There are circumstances where objects from the
Coral system will become exposed to the general Internet. In these
cases, the use of the Coral namespace will provide general
interoperability benefits to the Internet at large. Additionally,
there may be subcomponents of the Coral 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-Coral based, systems.
5. Security Considerations
Since there is no defined resolution mechanism for Coral 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.
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 2396, August 1998.
6.2. Informative References
[3] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[4] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml,
October 2000, <http://www.w3.org/TR/REC-xml>.
[5] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", W3C
REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-
names>.
[6] Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML
Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001,
<http://www.w3.org/TR/xmlschema-1/>.
7. Intellectual Property Statement
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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
8. Author's Address
Knox Carey
Intertrust Technologies Corporation
955 Stewart Drive
Sunnyvale, CA 94085
USA
Phone: +1 408 616 1666
EMail: knox@intertrust.com
URI: http://www.intertrust.com
9. Full Copyright Statement
Copyright (C) The Internet Society (2005).
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 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
