| 0,0 → 1,23 |
|---|
| [1.3.6.1.4.1.37476.2.5.1.1.2] |
| |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 identifier:stringToNumber |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 unicodelabel:StringToNumber |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 allocated:daniel-marschall@viathinksoft.de 2014-12-09 |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 description: StN (String to Number) algorithm |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: The StN (String to Number) algorithm works as follows: |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: If the input string is empty, the resulting number will be 99. |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: If the input string is not empty, then it will be |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: encoded using UTF-8 and finally encoded with Base64. |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: Every Base64 will be encoded to a two digit decimal number. |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: 'A' encodes to 00, 'B' encodes to 01, ..., |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: '/' encodes to 63, '=' encodes to 64 |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: All numbers will be concatenated. |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: Example: |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: 'test' will encode to '2906215129006464' |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: Using the StN algorithm, every string, or identifier respectively, |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: can be mapped into the OID tree (but the client must use |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: BigInteger to handle the OID, or read the OID as String |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: instead of interprete each arc as integer). |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: The advantage in comparison to name based Universally Unique Identifiers (UUIDs), which can be |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: mapped to the OID tree into arc 2.25 is, that the OID |
| oid:.1.3.6.1.4.1.37476.3.2.3.1 information: can be converted back to its original string. |