RFC 3001: A URN Namespace of Object Identifiers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3061.
Current version: RFC 3061 — A URN Namespace of Object Identifiers
In plain English — editorial summary, not part of the RFC
This document describes a Uniform Resource Names (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3001
- Published
- November 2000
- Authors
- M. Mealling
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
- Obsoleted by:
- RFC 3061
Topics
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.
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 2141URN SyntaxObsoleted
May 1997
- RFC 3043The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and OrganizationsCurrent
January 2001
- RFC 3085URN Namespace for NewsML ResourcesCurrent
March 2001
- RFC 3087Control of Service Context using SIP Request-URICurrent
April 2001
- RFC 3120A URN Namespace for XML.orgCurrent
June 2001
- RFC 3121A URN Namespace for OASISCurrent
June 2001
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?