Support the extensions in CCC Digital Key Specification

[xipki]

CCC defines in its Digital Key Specification 10 extensions, most of them have simple extension value:

ExternalCACertificateExtensionSchema ::= SEQUENCE
{
  extension_version INTEGER (1..255)
}

Below is the complete list of extension OIDs:

B.2.2 OID Assignment

Each certificate shall be identifiable by the following OID values:

• Vehicle Public Key Certificates (leaf) [K]
  1.3.6.1.4.1.41577.5.1
• External CA Certificates (intermediate)[F]
  1.3.6.1.4.1.41577.5.2
• Instance CA Certificates (intermediate) [E]
  1.3.6.1.4.1.41577.5.3
• Endpoint Certificates (leaf)[H]
  1.3.6.1.4.1.41577.5.4
• Vehicle OEM Encryption Certificate (VehicleOEM.Enc.Cert)
  1.3.6.1.4.1.41577.5.5
• Vehicle OEM Signature Certificate (VehicleOEM.Sig.Cert)
  1.3.6.1.4.1.41577.5.6
• Device.Enc.Cert (optional as only the PK is sent in the trackKey request)
  1.3.6.1.4.1.41577.5.7
• Vehicle Intermediate Certificate
  1.3.6.1.4.1.41577.5.8
• Vehicle OEM CA Certificate [J]
  1.3.6.1.4.1.41577.5.9
• Vehicle OEM CA Certificate (Signed by Device OEM CA) [M] (optional as only used by some 4 implemenation)
  1.3.6.1.4.1.41577.5.10

Extensions with the above OIDs shall be marked as critical.

CCC digital key is widely adopted in automotive, and I think Automotive is one of the most important application areas of C509, please add the support if possible. If the authors decide to support it, I can propose the syntax of the extension value.

[gselander]

If any of these are important to use with C509 then we should prioritize to add them. Is C509 relevant for automotive industry?

• Is this relevant for CCC Digital Key Specification (grant access to car e.g. from smart phone)? (Joel, Shahid, Lijun checks)

• Is this relevant for V2G (plug and charge)? (Martin checks)

( V2X probably not, based on IEEE )