RFC 3001

A URN Namespace of Object Identifiers

📅 published November 2000, from ietf

RFC 3001: A URN Namespace of Object Identifiers ✨

Network Working Group 🌸 Author: Michael Mealling, Network Solutions, Inc. 💖 Category: Informational 🧚 Date: November 2000 📅 Obsoletes: none listed 🙅‍♀️ Updates: none listed 🙅‍♀️

Status of this Memo 🎀

Okay so this memo is just info for the Internet community, bestie. It is NOT a standard of any kind, and the distribution is totally unlimited 🌈

Copyright (C) The Internet Society (2000). All Rights Reserved. 🔒

Abstract 🦋

This doc describes a Uniform Resource Names (URN) namespace called Object Identifiers (OIDs). 💜

1. Introduction ✨

Okay, so an Object Identifier is basically a series of digits that are separated in some way. The vibe is that once an entity gets an OID, it has total control to subdelegate further from that OID. Main character energy 👑 Some examples:

  • 1.3.6.1 - the Internet OID 🌐
  • 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs and such things 🏢
  • 1.3.6.1.2.1.27 - The Applications MIB 📱
  • 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-1274. 📚

This document specifies the oid URN namespace [1]. It's for encoding an Object Identifier as specified in ASN.1 [2] as a URI. 🎀

The namespace specification is for a formal namespace. 💅

2. Specification Template 🌷

Namespace ID:

"oid" requested. 🦋

Registration Information:

Registration Version Number: 1
Registration Date: 2000-04-30

Declared registrant of the namespace:

Okay this one is literally so awkward 🙈 I need help here. I'm not comfortable being the "registrant." So who do I actually put here?

The ISO/IEC Joint Technical Committee 1 - SubCommittee 6 is the answer, I think. The actual real authority is the ASN.1 specification itself, but right now SC6 is the committee that has the authority to interpret what that means. 🧠

Declaration of structure:

The NSS portion of the identifier follows the string encoding rules found in RFC 1778 Section 2.15 [3]. That spec says it's a series of digits separated by a period, with the most significant digit on the left and the least significant on the right. ✨

No changes are anticipated, since Object Identifiers are fairly simple and have been standardized with no changes for many years. Iconic stability 💎

Relevant ancillary documentation:

Relevant documentation can be found in X.660/Amd 2 | ISO/IEC 9834-1/Amd 2 [2]. 📖

Identifier uniqueness considerations:

The rules for assigning OIDs require that each OID be unique to the OID space, and that it can't be reassigned or reused. By reference, this URN namespace inherits those rules. 🔐

Identifier persistence considerations:

The rules about using OIDs require that they not be reused once assigned. By reference, this URN namespace inherits those rules too. 🫶

Process of identifier assignment:

Once an OID is assigned to some entity, that entity can then create and assign new OIDs below that particular OID. There are multiple entities that assign new OIDs to the general public. The top three levels are pre-assigned like this:

0 - ITU-T assigned
1 - ISO assigned
2 - Joint ISO/ITU-T assignment

Several assigned OIDs that are important to the Internet are:

1.3.6.1 - the Internet OID
1.3.6.1.4.1 - IANA-assigned company OIDs, used for private
              MIBs and such things

Process of identifier resolution:

At this time, no resolution mechanism is defined. Not yet, bestie 🤷‍♀️

Rules for Lexical Equivalence:

OIDs are made up of multiple occurrences of digits and the "." character. Lexical equivalence is achieved by an exact string match. 🎯

Conformance with URN Syntax:

There are no additional characters reserved. Clean 🧼

Validation mechanism:

None. 🫠

Scope:

Global 🌍

3. Examples 🍓

The following examples are taken from the example OIDs in the 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 Considerations 💀

Okay, this section is short but it's giving serious 😭 None, not already inherent to using unverifiable OIDs.

5. Acknowledgements 🫶

The author would like to thank Harald Alvestrand for the use of his OID database as a source for examples and references. Iykyk, he's a legend 👑

References 📚

[1]  Moats, R., "URN Syntax", RFC 2141, May 1997.

[2]  CCITT, "Specification of Basic Encoding Rules for Abstract
     Syntax Notation One (ASN.1)", CCITT Recommendation X.209,
     January 1988.

[3]  Howes, T., Kille, S., Yeong, W. and C. Robbins, "The String
     Representation of Standard Attribute Syntaxes", RFC 1778, March
     1995.

Author's Address 🏠

Michael Mealling
Network Solutions, Inc.
505 Huntmar Park Drive
Herndon, VA  22070
US

Phone: +1 770 935 5492
EMail: michaelm@netsol.com
URI:   http://www.netsol.com

Copyright (C) The Internet Society (2000). All Rights Reserved.

Okay so this document, and translations of it, may be copied and furnished to others. Derivative works that comment on or otherwise explain it, or help with implementing it, may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind. That's allowed as long as the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, like removing the copyright notice or references to the Internet Society or other Internet organizations. The exception is when it's needed for developing Internet standards, in which case the procedures for copyrights defined in the Internet Standards process must be followed, or when it's needed to translate it into languages other than English. 🌐

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. Forever and ever 💜

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. No cap, that's a lot of disclaimers 😭

Acknowledgement 🌸

Funding for the RFC Editor function is currently provided by the Internet Society. 🫶

📦 where this page comes from