query: oid:1.3.6.1.4.1.37476.9001$format=text result: Found object: oid:1.3.6.1.4.1.37476.9001 status: Information available name: MAC (OUI/EUI or CID/ELI) address based OIDs description: OIDs can be generated using an IEEE company description: identification (OUI or CID) or using an NUI (an NUI-48 is description: a 48-bit NUI that is an EUI-48, ELI-48, SAI-48, or description: AAI-48), such as the MAC address of a device. description: Construction rule: description: 1.      The first arc is the number of bits that will description: follow in the next arc. description: 2.      Since many OID implementations have size description: limitations description: (https://misc.daniel-marschall.de/asn.1/oid_facts.html#chap4) for description: arcs, an arc longer than 24 bits should be split up into description: 2 arcs (see example below). description: Examples: description: 1.      An OUI (MA-L) address has 24 bits, hence the description: owner of the OUI AA-BB-CC (in decimal 11189196) will gain description: ownership over the OID 1.3.6.1.4.1.37476.9001.24.11189196 description: 2.      An EUI-48 (usual MAC address for devices) could description: be AA-BB-CC-DD-EE-FF (in decimal 187723572702975). The description: arcs would split up into AA-BB-CC (in decimal 11189196) description: and 0xDDEEFF (in decimal 14544639). Hence, the owner of description: that device will gain ownership over the OID description: 1.3.6.1.4.1.37476.9001.48.11189196.14544639 description: Requirements: description: 1.      Most MAC-based identifiers can be used, but they description: must be defined by IEEE. description: 2.      They must be unique and unambiguous, because description: non-unique MAC-based identifiers cannot be encoded into description: an unique OID. Hence, AAI and Administrator CID are NOT description: allowed, because they are not worldwide unique and SAI description: may only be used if it is worldwide unique (depending on description: the IEEE standard defining the SAI). description: 3.      In case the OID is based on an actual device / description: network card, the ownership of the OID is lost if the description: device / card is given to someone else. description: Examples of IEEE identifiers are: description: description: IEEE Registrations description: description: CID*** description: OUI (MA-L) description: MA-M* description: OUI-36 (MA-S) description: IAB (deprecated) description: description: description: EUI (OUI + Vendor part) description: description: OUI-22 (deprecated) description: EUI-48 / MAC-48** (deprecated term) description: EUI-60 (deprecated) description: EUI-64 description: description: Regular EUI-64 description: MAC/EUI-48 to EUI-64 encapsulation (deprecated, description: because duplicate EUI-64 can be formed description: (https://www.ieee802.org/1/files/public/docs2014/as-garner-impact-of-new-OUI-tier-structure-on-1588-and-802-1as.pdf)) description: description: description: description: description: ELI*** (CID + Vendor part) description: description: ELI-48 description: ELI-64 description: description: description: CDI (OUI + Vendor part) description: description: CDI-30 (deprecated) description: CDI-32  description: CDI-40 (deprecated) description: TCDI-40 description: description: description: AAI are NOT allowed, because they are not worldwide description: unique. description: SAI may only be used if it is worldwide unique (depending description: on the IEEE standard defining the SAI). description: description:   description: * IEEE recommends not to use the 28-bit identifier MA-M description: to identify a company description: (https://www.ieee802.org/1/files/public/docs2014/as-garner-impact-of-new-OUI-tier-structure-on-1588-and-802-1as.pdf), description: but we don't see any reason why not to do it, since the description: MA-M prefix is unique and unambiguous. description: ** You can generate an OID using the MAC of your network description: card, but then you must make sure that nobody else can description: use that network card, otherwise they could use it to description: generate an OID that you have previously defined. In description: other words: If you have created an OID using your MAC description: address, then you will lose the permission to use the OID description: namespace once you give/sell the network card to someone description: else. description: *** IEEE defines "Administrator CIDs" (e.g. 3AA3F8, description: CA30BF, 4A07D6, FA94F1) which are not assigned description: exclusively, to allow local administrators to create description: ELIs. These CIDs and their constructed ELIs must not be description: used to create an OID, because the resulting OID will be description: ambiguous! url: https://hosted.oidplus.com/viathinksoft/?goto=oid%3A1.3.6.1.4.1.37476.9001 asn1-notation: { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 37476 mac-based(9001) } iri-notation: /ISO/Identified-Organization/6/1/4/1/37476/MacBased identifier: mac-based unicode-label: MacBased canonical-identifier: oid:1.3.6.1.4.1.37476.9001 handle-identifier: oid:1.3.6.1.4.1.37476.9001 alternate-identifier: aid:D276000186B20005005E3AD63BA93818 alternate-identifier: aid:D276000186F62B0601040182A464C629 alternate-identifier: guid:005e3ad6-4f46-8000-a6d3-9e454210b302 alternate-identifier: guid:1d7f1f6a-f906-5d63-9028-0437b67bb9fc alternate-identifier: guid:865fc051-2139-3f82-8e72-1bcd0a2ef00a alternate-identifier: mac:D2-21-BB-A9-38-18 alternate-identifier: mac:D3-21-BB-A9-38-18 alternate-identifier: weid:P-SX0-6Y1-2 alternate-identifier: x500dn:/dc=com/dc=example/cn=oidplus/1.3.6.1.4.1.37476.2.5.2.9.4.1=6175446/1.3.6.1.4.1.37476.2.5.2.9.4.2=1000945688 parent: oid:1.3.6.1.4.1.37476 created: 2025-07-24 21:42:00 updated: 2025-07-24 21:58:18 ra: ViaThinkSoft ra-status: Information available ra-contact-name: Daniel Marschall (ViaThinkSoft) ra-address: Germany ra-email: oidra@viathinksoft.de ra-updated: 2019-05-17 08:47:23 % -----BEGIN RSA SIGNATURE----- % dqtnIA7QsFJwsNaRSsRpVNsQ5U/2HKmrUiPj14ro+yWHdA2/8CA7+fappOxkNWrXmfjH5KPUQHtnEl % Z3zeJiffCyqE51S6e1ynJmGSZRtaGNMXntKqPNQxfaho2QLft22tCBx3gmmYINX39Uf9i8jOcz/41u % ZZjboDHBFKde5gUN97zHE+ttAqNu5nxswC4ir2Vh49BWMm6fHZx8R49RdUtAl4/WpoyhQDmjMhhsV2 % W8ubyNCYrh+9EKis9Cv6jm5lWeUz8lBhnarohIu8EOCv5FzooA4dkd5uRrS/iEyW+vJ/dYgzpC5ED6 % YLUBDlGgsmUu6pVqyqxuaity3uqflw== % -----END RSA SIGNATURE-----