draft-ietf-urn-nid-req-07.txt   draft-ietf-urn-nid-req-08.txt 
Internet Draft Leslie L. Daigle Internet Draft Leslie L. Daigle
October 20, 1998 Bunyip Information Systems March 31, 1999 Bunyip Information Systems
draft-ietf-urn-nid-req-07.txt Dirk-Willem van Gulik draft-ietf-urn-nid-req-08.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
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance
documents of the Internet Engineering Task Force (IETF), its with all provisions of Section 10 of RFC2026.
areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. 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 Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
To view the entire list of current Internet-Drafts, please check The list of current Internet-Drafts can be accessed at
the "1id-abstracts.txt" listing contained in the Internet-Drafts
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net http://www.ietf.org/ietf/1id-abstracts.txt
(Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East
Coast), or ftp.isi.edu (US West Coast). The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
0.0 Abstract 0.0 Abstract
The URN WG has defined a syntax for Uniform Resource Names The URN WG has defined a syntax for Uniform Resource Names
(URNs) [RFC2141], as well as some proposed mechanisms for their (URNs) [RFC2141], as well as some proposed mechanisms for their
resolution and use in Internet applications ([RFC2168, RFC2169]). resolution and use in Internet applications ([RFC2168, RFC2169]).
The whole rests on the concept of individual "namespaces" within the The whole rests on the concept of individual "namespaces" within the
URN structure. Apart from proof-of-concept namespaces, the use URN structure. Apart from proof-of-concept namespaces, the use
of existing identifiers in URNs has been discussed ([RFC2288]), of existing identifiers in URNs has been discussed ([RFC2288]),
and this document lays out general definitions of and and this document lays out general definitions of and
skipping to change at line 355 skipping to change at line 359
No provision is made for avoiding collision of experimental No provision is made for avoiding collision of experimental
NIDs; they are intended for use within internal or limited NIDs; they are intended for use within internal or limited
experimental contexts. experimental contexts.
As there is no registration, no registration maintenance As there is no registration, no registration maintenance
procedures are needed. procedures are needed.
II. Informal: These are registered with IANA and are assigned a II. Informal: These are registered with IANA and are assigned a
number sequence as an identifier, in the format: number sequence as an identifier, in the format:
"iana-" <number> "urn-" <number>
where <number> is chosen by the IANA on a First Come First where <number> is chosen by the IANA on a First Come First
Served basis (see [IANA-CONSIDERATIONS]). Served basis (see [IANA-CONSIDERATIONS]).
Registrants should send a copy of the registration Registrants should send a copy of the registration
template (see section 3.0), duly completed, to the template (see section 3.0), duly completed, to the
urn-nid@apps.ietf.org urn-nid@apps.ietf.org
mailing and allow for a 2 week discussion period for mailing and allow for a 2 week discussion period for
skipping to change at line 406 skipping to change at line 410
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 be an already-registered NID . not be an already-registered NID
. not start with "x-" (see Type I above) . not start with "x-" (see Type I above)
. not start with "iana-" (see Type II above) . not start with "urn-" (see Type II above)
. not start with "XY-", where XY is any . not start with "XY-", where XY is any
combination of 2 ASCII letters (see NOTE, below) combination of 2 ASCII letters (see NOTE, below)
. be more than 2 letters long . be more than 2 letters long
NOTE: ALL two-letter combinations, and two-letter combinations NOTE: ALL two-letter combinations, and two-letter combinations
followed by "-" and any sequence of valid NID characters, are followed by "-" and any sequence of valid NID characters, are
reserved for potential use as countrycode-based NIDs for reserved for potential use as countrycode-based NIDs for
eventual national registrations of URN namespaces. The eventual national registrations of URN namespaces. The
definition and scoping of rules for allocation of responsibility definition and scoping of rules for allocation of responsibility
for such namespaces is beyond the scope of this document. for such namespaces is beyond the scope of this document.
skipping to change at line 575 skipping to change at line 579
[RFC1737] Karen R Sollins & Larry Masinter, "Functional Requirements [RFC1737] Karen R Sollins & Larry Masinter, "Functional Requirements
for Uniform Resource Names", RFC1737, December 1994 for Uniform Resource Names", RFC1737, December 1994
[RFC2276] K. Sollins, "Architectural Principles of Uniform Resource [RFC2276] K. Sollins, "Architectural Principles of Uniform Resource
Name Resolution", RFC 2276, January 1998. Name Resolution", RFC 2276, January 1998.
8.0 Authors' Addresses 8.0 Authors' Addresses
Leslie L. Daigle Leslie L. Daigle
Bunyip Information Systems Inc Bunyip Information Systems Inc
310 Ste. Catherine St. W 147 St. Paul St. West
Suite 300 Suite 200
Montreal, Quebec, CANADA Montreal, Quebec, CANADA
H2X 2A1 H2Y 1Z5
voice: +1 514 875-8611 voice: +1 514 285-0088
fax: +1 514 875-8134 fax: +1 514 285-4515
email: leslie@bunyip.com email: leslie@bunyip.com
Dirk-Willem van Gulik Dirk-Willem van Gulik
ISIS/STA/CEO - TP 270 ISIS/STA/CEO - TP 270
Joint Research Centre Ispra Joint Research Centre Ispra
21020 Ispra (Va) 21020 Ispra (Va)
Italy. Italy.
voice: +39 332 78 9549 or 5044 voice: +39 332 78 9549 or 5044
fax: +39 332 78 9185 fax: +39 332 78 9185
email: Dirk.vanGulik@jrc.it email: Dirk.vanGulik@jrc.it
 End of changes. 8 change blocks. 
19 lines changed or deleted 23 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/