draft-ietf-urn-nid-req-06.txt   draft-ietf-urn-nid-req-07.txt 
Internet Draft Leslie L. Daigle Internet Draft Leslie L. Daigle
October 8, 1998 Bunyip Information Systems October 20, 1998 Bunyip Information Systems
draft-ietf-urn-nid-req-06.txt Dirk-Willem van Gulik draft-ietf-urn-nid-req-07.txt Dirk-Willem van Gulik
ISIS/CEO, JRC Ispra ISIS/CEO, JRC Ispra
Renato Iannella Renato Iannella
DSTC Pty Ltd DSTC Pty Ltd
Patrik Faltstrom Patrik Faltstrom
Tele2/Swipnet Tele2/Swipnet
URN Namespace Definition Mechanisms URN Namespace Definition Mechanisms
Status of this Document Status of this Document
skipping to change at line 89 skipping to change at line 89
For the purposes of URNs, a "namespace" is a collection of For the purposes of URNs, a "namespace" is a collection of
uniquely-assigned identifiers. A URN namespace itself has an uniquely-assigned identifiers. A URN namespace itself has an
identifier in order to identifier in order to
. ensure global uniqueness of URNs . ensure global uniqueness of URNs
. (where desired) provide a cue for the structure of the . (where desired) provide a cue for the structure of the
identifier identifier
For example, ISBNs and ISSNs are both collections of identifiers used For example, ISBNs and ISSNs are both collections of identifiers used
in the traditional publishing world; while there may some number (or in the traditional publishing world; while there may be some number (or
numbers) that is both a valid ISBN identifier and ISSN identifier, numbers) that is both a valid ISBN identifier and ISSN identifier,
using different designators for the two collections ensures that no using different designators for the two collections ensures that no
two URNs will be the same for different resources. two URNs will be the same for different resources.
The development of an identifier structure, and thereby a collection The development of an identifier structure, and thereby a collection
of identifiers, is a process that is inherently dependent on the of identifiers, is a process that is inherently dependent on the
requirements of the community defining the identifier, how they will requirements of the community defining the identifier, how they will
be assigned, and the uses to which they will be put. All of these be assigned, and the uses to which they will be put. All of these
issues are specific to the individual community seeking to define a issues are specific to the individual community seeking to define a
namespace (e.g., publishing community, association of booksellers, namespace (e.g., publishing community, association of booksellers,
skipping to change at line 316 skipping to change at line 316
Scope: Scope:
This section should outline the scope of the use of the This section should outline the scope of the use of the
identifiers in this namespace. Apart from considerations identifiers in this namespace. Apart from considerations
of private vs. public namespaces, this section is critical of private vs. public namespaces, this section is critical
in evaluating the applicability of a requested NID. For in evaluating the applicability of a requested NID. For
example, a namespace claiming to deal in "social security example, a namespace claiming to deal in "social security
numbers" should have a global scope and address all numbers" should have a global scope and address all
social security number structures (unlikely). On the social security number structures (unlikely). On the
other hand, at a national level, it is reasonable to other hand, at a national level, it is reasonable to
posit a URN namespace for "this nation's social security propose a URN namespace for "this nation's social security
numbers". numbers".
4.0 URN Namespace Registration, Update, and NID Assignment Process 4.0 URN Namespace Registration, Update, and NID Assignment Process
Different levels of disclosure are expected/defined for namespaces. Different levels of disclosure are expected/defined for namespaces.
According to the level of open-forum discussion surrounding According to the level of open-forum discussion surrounding
the disclosure, a URN namespace may be assigned or may request a the disclosure, a URN namespace may be assigned or may request a
particular identifier. The [IANA-CONSIDERATIONS] document suggests particular identifier. The [IANA-CONSIDERATIONS] document suggests
the need to specify update mechanisms for registrations -- who the need to specify update mechanisms for registrations -- who
is given the authority to do so, from time to time, and what are is given the authority to do so, from time to time, and what are
skipping to change at line 403 skipping to change at line 403
urn-nid@apps.ietf.org urn-nid@apps.ietf.org
mailing list to allow for a 2 week discussion period for mailing list to allow for a 2 week discussion period for
clarifying the expression of the registration information, clarifying the expression of the registration information,
before the IESG progresses the document to RFC status. before the IESG progresses the document to RFC status.
A particular NID string is requested, and is assigned by IETF A particular NID string is requested, and is assigned by IETF
consensus (as defined in [IANA-CONSIDERATIONS]), with consensus (as defined in [IANA-CONSIDERATIONS]), with
the additional constraints that the NID string must the additional constraints that the NID string must
not start with "x-" (see Type I above) or "iana-" (see Type II
above), is not already a registered NID, and is more
than 2 letters long.
ALL two-letter combinations are reserved for use . not be an already-registered NID
as country code NIDs for eventual national registrations of . not start with "x-" (see Type I above)
URN namespaces. . not start with "iana-" (see Type II above)
. not start with "XY-", where XY is any
combination of 2 ASCII letters (see NOTE, below)
. be more than 2 letters long
NOTE: ALL two-letter combinations, and two-letter combinations
followed by "-" and any sequence of valid NID characters, are
reserved for potential use as countrycode-based NIDs for
eventual national registrations of URN namespaces. The
definition and scoping of rules for allocation of responsibility
for such namespaces is beyond the scope of this document.
Registrations may be updated by updating the RFC through Registrations may be updated by updating the RFC through
standard IETF RFC update mechanisms. Thus, proposals for standard IETF RFC update mechanisms. Thus, proposals for
updates may be made by the original authors, other IETF updates may be made by the original authors, other IETF
participants, or the IESG. In any case, the proposed participants, or the IESG. In any case, the proposed
updated template must be circulated on the urn-nid updated template must be circulated on the urn-nid
discussion list, allowing for a 2 week review period. discussion list, allowing for a 2 week review period.
URN namespace registrations will be posted in the anonymous FTP directory URN namespace registrations will be posted in the anonymous FTP directory
"ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/". "ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/".
5.0 Example 5.0 Example
The following example is provided for the purposes of illustration of The following example is provided for the purposes of illustration of
the URN NID template described in section 3.0. Although it is based on the URN NID template described in section 3.0. Although it is based on
a posited "generic Internet namespace" that has been discussed informally a hypothetical "generic Internet namespace" that has been discussed informally
within the URN WG, there are still technical and infrastructural issues within the URN WG, there are still technical and infrastructural issues
that would have to be resolved before such a namespace could be properly that would have to be resolved before such a namespace could be properly
and completely described. and completely described.
Namespace ID: Namespace ID:
To be assigned To be assigned
Registration Information: Registration Information:
 End of changes. 6 change blocks. 
11 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/