BCP 33, RFC 2611 on URN Namespace Definition Mechanisms

RFC Editor <rfc-ed@ISI.EDU> Mon, 14 June 1999 18:21 UTC

Message-Id: <199906141755.KAA10577@boreas.isi.edu>
To: IETF-Announce:;
Subject: BCP 33, RFC 2611 on URN Namespace Definition Mechanisms
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 14 Jun 1999 10:55:02 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        BCP 33:
	RFC 2611:

        Title:	    URN Namespace Definition Mechanisms
	Author(s):  L. Daigle, D. van Gulik, R. Iannella, P. Falstrom
        Status:     Best Current Practice
	Date:       June 1999
        Mailbox:    leslie@thinkingcat.com, Dirk.vanGulik@jrc.it,
		    renato@dstc.edu.au, paf@swip.net
        Pages:      14
        Characters: 26916
        Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-ietf-urn-nid-req-08.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2611.txt


The URN WG has defined a syntax for Uniform Resource Names (URNs)
[RFC2141], as well as some proposed mechanisms for their resolution
and use in Internet applications ([RFC2168, RFC2169]).  The whole
rests on the concept of individual "namespaces" within the URN
structure.  Apart from proof-of-concept namespaces, the use of
existing identifiers in URNs has been discussed ([RFC2288]), and this
document lays out general definitions of and mechanisms for
establishing URN "namespaces".

This document is a product of the Uniform Resource Names Working Group
of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2611.txt"><ftp://ftp.isi.edu/in-notes/rfc2611.txt>

BCP 33, RFC 2611 on URN Namespace Definition Mech… RFC Editor