metasystema.org
ObsoletedBEST CURRENT PRACTICEIETF streamBCP33

RFC 2611: URN Namespace Definition Mechanisms

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3406.

Current document in this lineage: RFC 8141 — Uniform Resource Names (URNs)

In plain English — editorial summary, not part of the RFC

This document lays out general definitions of and mechanisms for establishing URN "namespaces". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC2611
Published
June 1999
Authors
L. Daigle; D. van Gulik; R. Iannella; P. Faltstrom
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
app
Pages
14
Also known as
BCP33
Obsoleted by:
RFC 3406

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 2141 (1997)
  2. RFC 2611 (1999)
  3. RFC 3406 (2002)
  4. RFC 8141 (2017) ✓

Read the full history of Uniform Resource Names (URNs) →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2611-urn-namespace-definition-mechanisms