RFC 3406
Uniform Resource Names (URN) Namespace Definition Mechanisms, October 2002
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Obsoletes:
- RFC 2611
- Obsoleted by:
- RFC 8141
- Authors:
- L. Daigle
D. van Gulik
R. Iannella
P. Faltstrom - Stream:
- IETF
- Source:
- urn (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3406
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3406
Abstract
This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. 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 in RFC 2288. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.