As per Relevance of the word identifier, we have this rfc below:
Network Working Group M.
Request for Comments: 3061
Category: Informational February 2001
Obsoletes: 3001
A URN Namespace of Object
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document describes a Uniform Resource Name (URN) namespace
contains Object Identifiers (OIDs). It obsoletes RFC 3001.
1.
An Object Identifier is a tree of nodes where each node is simply
sequence of digits. The rules roughly state that once an entity
assigned a node in the Object Identifier (OID) tree, it has
discretion to further subdelegate sub-trees off of that node.
examples of OIDs include
o 1.3.6.1 - the Internet
o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private
and such
o 1.3.6.1.2.1.27 - The Applications
o 0.9.2342.19200300.100.4 - Object ID's used in the directory
project to identify X.500 Object Classes. Mostly defined in
1274.
This document specifies the "oid" URN namespace [2]. This
is for encoding an Object Identifier as specified in ASN.1 [3] as
URI. RFC 3001 [1] 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
Namespace ID
"oid" requested
Registration Information
Registration Version Number: 1
Registration Date: 2000-04-30
Declared registrant of the namespace
The ISO/IEC Joint Technical Committee 1 - SubCommittee 6
The real authority is the ASN.1 specification itself but SC6
the committee that has the authority to interpret what
means, thus that committee is listed as the registrant
Declaration of structure
The NSS portion of the identifier is based on the string
rules found in RFC 1778 Section 2.15 [4] which specifies a
of digits separated by a period with the most significant
being at the left and the least significant being at the right
At no time shall the NSS portion of the URN contain the
readable description of a particular node in the OID tree.
NSS portion of the name is strictly limited to the digits 0-9
the '.' character with no leading zeros. No other characters
permitted. This is all expressed in the following ABNF
oid = number *( DOT number )
number = DIGIT / ( LEADDIGIT 1*DIGIT )
LEADDIGIT = %x31-39 ; 1-9
DIGIT = %x30 / LEADDIGIT ; 0-9
DOT = %x2E ;
No changes are anticipated since Object Identifiers are
simple and have been standardized with no changes for many years
Relevant ancillary documentation
Relevant documentation can be found in X.660/Amd 2 | ISO/
9834-1/Amd 2[3].
Mealling Informational [Page 2]
RFC 3061 OID URN Namespace February 2001
Identifier uniqueness considerations
The rules for assignment of OIDs requires that each OID be
to the OID space and that it cannot be reassigned or reused.
reference this URN namespace inherents those rules
Identifier persistence considerations
The rules concerning the use of OIDs requires that they not
reused once assigned. By reference this URN namespace
those rules
Process of identifier assignment
Once an OID is assigned to some entity, that entity can
create and assign new OIDs below that particular OID. There
multiple entities that assign new OIDs to the general public.
top three levels are pre-assigned as follows
0 - ITU-T
1 - ISO
2 - Joint ISO/ITU-T
several assigned OIDs that are of importance to the Internet are
1.3.6.1 - the Internet
1.3.6.1.4.1 - IANA-assigned company OIDs, used for
MIBs and such
Process of identifier resolution
At this time no resolution mechanism is defined
Rules for Lexical Equivalence
OIDs are composed of multiple occurrences of digits and the "."
character. Lexical equivalence is achieved by exact string match
Conformance with URN Syntax
There are no additional characters reserved
Validation mechanism
None
Mealling Informational [Page 3]
RFC 3061 OID URN Namespace February 2001
Scope
3.
The following examples are taken from the example OIDs from
Introduction
urn:oid:1.3.6.1
urn:oid:1.3.6.1.4.1
urn:oid:1.3.6.1.2.1.27
URN:OID:0.9.2342.19200300.100.4
4. Security
None not already inherent to using unverifiable OIDs
5.
The author would like to thank Harald Alvestrand for the use of
OID database as a source for examples and references
[1] Mealling, M., "A URN Namespace of Object Identifiers", RFC 3001,
November 2000.
[2] Moats, R., "URN Syntax", RFC 2141, May 1997.
[3] CCITT, "Specification of Basic Encoding Rules for
Syntax Notation One (ASN.1)", CCITT Recommendation X.209,
January 1988.
[4] Howes, T., Kille, S., Yeong, W. and C. Robbins, "The
Representation of Standard Attribute Syntaxes", RFC 1778,
1995.
Mealling Informational [Page 4]
RFC 3061 OID URN Namespace February 2001
Author's
Michael
505 Huntmar Park
Herndon, VA 22070
Phone: +1 770 935 5492
EMail: michaelm@netsol.
URI: http://www.netsol.
Mealling Informational [Page 5]
RFC 3061 OID URN Namespace February 2001
Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Mealling Informational [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
