ViaThinkSoft Next Level Free OIDs

ViaThinkSoft defines allocation mechanisms for offering free Object Identifiers with and without registration. The mechanisms are in-sync with the allocations for ISO 7816 Application Identifiers offered by HickelSOFT and ViaThinkSoft ( see https://hosted.oidplus.com/viathinksoft/?goto=aid%3AD276000186F )

Ideas for more free OID and AID schemas can be sent to Daniel Marschall / ViaThinkSoft.

Schema	AID (ISO 7816-5)	OID (ISO 9834-1 / ITU-T X.660)
HickelSOFT Allocated	D2 76 00 01 86 A0	1.3.6.1.4.1.56776
ViaThinkSoft Allocated	D2 76 00 01 86 B0	1.3.6.1.4.1.37476
ViaThinkSoft Member	D2 76 00 01 86 B1	1.3.6.1.4.1.37476.1
ViaThinkSoft Product	D2 76 00 01 86 B2	1.3.6.1.4.1.37476.2
ViaThinkSoft Standard	D2 76 00 01 86 B3	1.3.6.1.4.1.37476.3
Example	D2 76 00 01 86 E0	2.999 (previously 1.3.6.1.4.1.37476.9999)
IANA PEN	D2 76 00 01 86 F0	1.3.6.1.4.1
ViaThinkSoft Free OID	D2 76 00 01 86 F1	1.3.6.1.4.1.37476.9000
MAC	D2 76 00 01 86 F2	1.3.6.1.4.1.37476.9001
Device vendor	D2 76 00 01 86 F3	1.3.6.1.4.1.37476.9002
Device vendor: USB	D2 76 00 01 86 F3 01	1.3.6.1.4.1.37476.9002.1
Device vendor: PCI	D2 76 00 01 86 F3 02	1.3.6.1.4.1.37476.9002.2
Identified Organization	D2 76 00 01 86 F4	1.3.6.1.4.1.37476.9003
Ident. Organization: DUNS	D2 76 00 01 86 F4 01	1.3.6.1.4.1.37476.9003.1
Ident. Organization: Ringgold	D2 76 00 01 86 F4 02	1.3.6.1.4.1.37476.9003.2
Ident. Organization: DOI	D2 76 00 01 86 F4 03	1.3.6.1.4.1.37476.9003.3
GS1	D2 76 00 01 86 F5	1.3.6.1.4.1.37476.9004
Short OID	D2 76 00 01 86 F6	(OID Root)
Identified Person	D2 76 00 01 86 F7	1.3.6.1.4.1.37476.9005
Identified Person: ISO 27729	D2 76 00 01 86 F7 01	1.3.6.1.4.1.37476.9005.1
Identified Person: ISNI	D2 76 00 01 86 F7 01 1x	1.3.6.1.4.1.37476.9005.1.1
Identified Person: ORCID	D2 76 00 01 86 F7 01 2x	1.3.6.1.4.1.37476.9005.1.2
ISO 6523 ICD	D2 76 00 01 86 F8	1.3.6.1.4.1.37476.9006
ISO 6523 ICD: EBID	D2 76 00 01 86 F8 00 BD	1.3.6.1.4.1.37476.9006.189

Free OIDs are offered by registration at www.viathinksoft.de/freeoid – the only requirement is a valid email address.

The owner will receive permissions to use the next available number below 1.3.6.1.4.1.37476.9000.

1.3.6.1.4.1.37476.9001 – MAC (OUI/EUI or CID/ELI) address based OIDs [AID: F2]

OIDs can be generated using an IEEE company identification (OUI or CID) or using an NUI (an NUI-48 is a 48-bit NUI that is an EUI-48, ELI-48, SAI-48, or AAI-48), such as the MAC address of a device.

Construction rule:

1. The first arc is the number of bits that will follow in the next arc.

2. Since many OID implementations have size limitations for arcs, an arc longer than 24 bits should be split up into 2 arcs (see example below).

Examples:

1. An OUI (MA-L) address has 24 bits, hence the owner of the OUI AA-BB-CC (in decimal 11189196) will gain ownership over the OID 1.3.6.1.4.1.37476.9001.24.11189196

2. An EUI-48 (usual MAC address for devices) could be AA-BB-CC-DD-EE-FF (in decimal 187723572702975). The arcs would split up into AA-BB-CC (in decimal 11189196) and 0xDDEEFF (in decimal 14544639). Hence, the owner of that device will gain ownership over the OID 1.3.6.1.4.1.37476.9001.48.11189196.14544639

Requirements:

1. Most MAC-based identifiers can be used, but they must be defined by IEEE.

2. They must be unique and unambiguous, because non-unique MAC-based identifiers cannot be encoded into an unique OID. Hence, AAI and Administrator CID are NOT allowed, because they are not worldwide unique and SAI may only be used if it is worldwide unique (depending on the IEEE standard defining the SAI).

3. In case the OID is based on an actual device / network card, the ownership of the OID is lost if the device / card is given to someone else.

Examples of IEEE identifiers are:

IEEE Registrations
- CID***
- OUI (MA-L)
- MA-M*
- OUI-36 (MA-S)
- IAB (deprecated)
EUI (OUI + Vendor part)
- OUI-22 (deprecated)
- EUI-48 / MAC-48** (deprecated term)
- EUI-60 (deprecated)
- EUI-64
  - Regular EUI-64
  - MAC/EUI-48 to EUI-64 encapsulation (deprecated, because duplicate EUI-64 can be formed)
ELI*** (CID + Vendor part)
- ELI-48
- ELI-64
CDI (OUI + Vendor part)
- CDI-30 (deprecated)
- CDI-32
- CDI-40 (deprecated)
- TCDI-40
AAI are NOT allowed, because they are not worldwide unique.
SAI may only be used if it is worldwide unique (depending on the IEEE standard defining the SAI).

* IEEE recommends not to use the 28-bit identifier MA-M to identify a company, but we don't see any reason why not to do it, since the MA-M prefix is unique and unambiguous.

** You can generate an OID using the MAC of your network card, but then you must make sure that nobody else can use that network card, otherwise they could use it to generate an OID that you have previously defined. In other words: If you have created an OID using your MAC address, then you will lose the permission to use the OID namespace once you give/sell the network card to someone else.

*** IEEE defines "Administrator CIDs" (e.g. 3AA3F8, CA30BF, 4A07D6, FA94F1) which are not assigned exclusively, to allow local administrators to create ELIs. These CIDs and their constructed ELIs must not be used to create an OID, because the resulting OID will be ambiguous!

1.3.6.1.4.1.37476.9002 – Device vendor based OIDs [AID: F3 xx]

1.3.6.1.4.1.37476.9002.1 – USB-IF (usb.org) VendorID based OIDs [AID: F3 01]

Every owner of a USB-IF Vendor Code can use an OID based on the following construction schema.

Construction schema:

1. The first arc is the number of bits that will follow.

2. In case the first arc has the value 16 (bits), the second arc will be the vendor ID converted to decimal and the third arc will be in the responsibility of the vendor, for any purpose.

3. In case the first arc has the value 32 (bits), the second arc will be the vendor ID converted to decimal, the third arc will be the product ID converted to decimal and the fourth arc will be the in the responsibility of the vendor, for the purpose of the given product.

Example: Microsoft has USB Vendor ID 0x045E (in decimal 1118) and offers the product “IntelliMouse” with Product ID 0x0009 (in decimal 9).

1. Microsoft may use 1.3.6.1.4.1.37476.9002.1.16.1118 for any purpose

2. Microsoft may use 1.3.6.1.4.1.37476.9002.1.32.1118.9 for anything based on the given product.

1.3.6.1.4.1.37476.9002.2 – PCI (pcsig.com) VendorID based OIDs [AID: F3 02]

Every owner of a PCI Vendor Code can use an OID based on the following construction schema.

Construction schema:

1. The first arc is the number of bits that will follow.

2. In case the first arc has the value 16 (bits), the second arc will be the vendor ID converted to decimal and the third arc will be in the responsibility of the vendor, for any purpose.

Example: Sectra AB has PCI Vendor ID 0x17E4 (in decimal 6116) and offers the product “KK672 Cardbus encryption board“ with Product ID 0x0002 (in decimal 2).

1. Sectra may use 1.3.6.1.4.1.37476.9002.2.16.6116 for any purpose

2. Sectra may use 1.3.6.1.4.1.37476.9002.2.32.6116.2 for anything based on the given product.

1.3.6.1.4.1.37476.9003 – Identified Organization based OIDs [AID: F4 xx]

1.3.6.1.4.1.37476.9003.1 – D-U-N-S based OIDs [AID: F4 01]

Example:

D-U-N-S number: 08-146-6849 (Microsoft)

Constructed OID: 1.3.6.1.4.1.37476.9003.1.8.146.6849

1.3.6.1.4.1.37476.9003.2 – Ringgold based OIDs [AID: F4 02]

Example:

RIN number: 5072 (Wellcome Trust)

Constructed OID: 1.3.6.1.4.1.37476.9003.2.5072

1.3.6.1.4.1.37476.9003.3 – DOI based OIDs [AID: F4 03]

Example:

DOI number: 10.1109 (IEEE)

Constructed OID: 1.3.6.1.4.1.37476.9003.3.10.1109

1.3.6.1.4.1.37476.9004 – GS1 based OIDs [AID: F5]

You can use any GS1 based number as long as it is unique. For example, you can use your GS1 company prefix, or the GLN describing your location, or the GTIN describing your product. You cannot use numbers like Production date (YYMMDD), since they are not unique.

Construction schema:

1. The first arc is the number of decimal digits that will follow.

2. Since many OID implementations have size limitations for arcs, an arc longer than 8 digits should be split up into 2 arcs (see example below).

Examples:

1. Global Company Prefix 0012000 (7 digits) equals OID 1.3.6.1.4.1.37476.9004.7.12000

2. GTIN 001200000017-1 has two representations:

a. 12 digits without check digit, split up into 00120000 and 0017, equals OID 1.3.6.1.4.1.37476.9004.12.120000.17

b. 13 digits including check digit, split up into 00120000 and 00171, equals OID 1.3.6.1.4.1.37476.9004.13.120000.171

3. GLN 001200000000-3 has two representations:

a. 12 digits without check digit, split up into 00120000 and 0000, equals OID 1.3.6.1.4.1.37476.9004.12.120000.0

b. 13 digits including check digit, split up into 00120000 and 00003, equals OID 1.3.6.1.4.1.37476.9004.13.120000.3

1.3.6.1.4.1.37476.9005 – Identified Person based OIDs [AID: F7 xx]

1.3.6.1.4.1.37476.9005.1 – ISO 27729 compatible schema based OIDs [AID: F7 01 x]

1.3.6.1.4.1.37476.9005.1.1 – International Standard Name Identifier (ISNI) based OIDs [AID: F7 01 1]

Example:

ISNI: 0000-0001-0929-6053 (Bill Gates)

OID: 1.3.6.1.4.1.37476.9005.1.1.0.1.929.6053

1.3.6.1.4.1.37476.9005.1.2 – Open Researcher and Contributor ID (ORCID) based OIDs [AID: F7 01 2]

Example:

ORCID: 0000-0002-1825-0097 (Josiah S. Carberry)

OID: 1.3.6.1.4.1.37476.9005.1.2.0.2.1825.97

1.3.6.1.4.1.37476.9006 – ISO 6523 ICD based OIDs [AID: F8 xx xx]

Construction Rule:
1. The first arc is the ISO 6523 ICD code.
2. The payload will be defined in the next arcs, as defined by ViaThinkSoft. (Suggestions for defining more ISO 6523 ICD payloads are welcome!)