A URN Namespace of Object Identifiers (RFC3061)
Original Publication Date: 2001-Feb-01
Included in the Prior Art Database: 2005-May-18
Internet Society Requests For Comment (RFCs)
This document describes a Uniform Resource Name (URN) namespace that contains Object Identifiers (OIDs). It obsoletes RFC 3001.
Network Working Group M.
Request for Comments: 3061 Verisign
Category: Informational February 2001
A URN Namespace of Object Identifiers
Status of this Memo
provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2001). All Rights Reserved.
describes a Uniform Resource Name (URN) namespace that
contains Object Identifiers (OIDs). It obsoletes RFC 3001.
Identifier is a tree of nodes where each node is simply a
sequence of digits. The rules roughly state that once an entity is
assigned a node in the Object Identifier (OID) tree, it has sole
discretion to further subdelegate sub-trees off of that node. Some
examples of OIDs include:
o 126.96.36.199 - the Internet OID
o 188.8.131.52.4.1 - IANA-assigned company OIDs, used for private MIBs
and such things
o 184.108.40.206.2.1.27 - The Applications MIB
o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot
project to identify X.500 Object Classes. Mostly defined in RFC
specifies the "oid" URN namespace . This namespace
is for encoding an Object Identifier as specified in ASN.1  as a
URI. RFC 3001  is obsoleted by this specification.
The namespace specification is for a formal namespace.
Mealling Informational [Page 1]
RFC 3061 OID URN Namespace February 2001
2. Specification Template
Version Number: 1
Registration Date: 2000-04-30
Declared registrant of the namespace:
The ISO/IEC Joint Technical Committee 1 - SubCommittee 6
authority is the ASN.1 specification itself but SC6 is
the committee that has the authority to interpret what that
means, thus that committee is listed as the registrant.
Declaration of structure:
portion of the identifier is based on the string encoding
rules found in RFC 1778 Section 2.15  which specifies a series
of digits separated by a period with the most significant digit
being at the left and the least significant being at the right.
At no time shall the NSS portion of the URN contain the human
readable description o...