idnits 2.17.1 draft-ietf-urn-rfc2611bis-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 66 4 RFC 3406 6 Title: Uniform Resource Names (URN) Namespace Definition 7 Mechanisms 8 Author(s): L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom 9 Status: Best Current Practice 10 Date: October 2002 11 Mailbox: leslie@thinkingcat.com, Dirkx@webweaving.org, 12 renato@iprsystems.com, paf@cisco.com 13 Pages: 22 14 Characters: 43707 15 Obsoletes: 2611 16 SeeAlso: BCP 66 18 I-D Tag: draft-ietf-urn-rfc2611bis-04.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3406.txt 22 This document lays out general definitions of and mechanisms for 23 establishing Uniform Resource Names (URN) "namespaces". The URN WG 24 has defined a syntax for URNs in RFC 2141, as well as some proposed 25 mechanisms for their resolution and use in Internet applications in 26 RFC 3401 and RFC 3405. The whole rests on the concept of individual 27 "namespaces" within the URN structure. Apart from proof-of-concept 28 namespaces, the use of existing identifiers in URNs has been discussed 29 in RFC 2288. 31 This document is a product of the Uniform Resource Names Working Group 32 of the IETF. 34 This document specifies an Internet Best Current Practices for the 35 Internet Community, and requests discussion and suggestions for 36 improvements. Distribution of this memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.