{ "status": 0, "status_bits": [], "ra_email": "", "comment": "Short OID based AID", "confidential": false, "title": "Short OID based AID", "description": "

Short OID based AID (no application-specific bits, since the OID should be application specific)

\n

The payload is the ASN.1 DER encoding of an Absolute OID, but without \"Type\" and \"Length\" bytes (to save space).
Note that you can only encode short OIDs which decode into a DER code of 12 bytes or less.
There is no application specific part, so you should define an OID which resembles your desired AID.

\n

Syntax:

\n
D2 76 00 01 86 F6 + DER Encoding of an ABSOLUTE OID without Type (max 10 bytes without type = 11 bytes DER)
\n

Steps how to generate such an AID:
1. Encode your Absolute OID to the ASN.1 DER format, e.g. using the tool https://misc.daniel-marschall.de/asn.1/oid-converter/online.php
    Requirements (otherwise it is not possible to use the OID as AID using this method):
    - The DER encoding must not exceed 11 bytes of length
    - If the DER encoding is exactly 11 bytes long, the last byte must not be FF (this would generate an AID which is reserved by ISO)
      This is always true for DER OID encodings, so there is nothing you need to worry about.
2. Replace the first byte of the DER encoding (value \"06\") with \"D2 76 00 01 86 F6\".

\n

Examples:

\n
D2 76 00 01 86 F6 02 88 37                       = AID for OID 2.999, which is {joint-iso-itu-t(2) example(999)}
D2 76 00 01 86 F6 07 60 86 48 01 65 64 01        = AID for OID 2.16.840.1.101.100.1, which is {joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) 100 1}
\n

Example for an OID that CANNOT be used:

\n

The OID 1.3.6.1.4.1.37476.9000.1 cannot be used because its DER encoding is 13 bytes long.

", "created": "2022-09-23 22:18:58", "updated": "2023-11-17 22:16:23", "children": [] }