ISO 15118-20: TLS 1.3 and certificates

Which TLS versions carry which protocol, the cipher suites, groups and signature algorithms of clause 7.7.3, and what a capture shows of it.

Which TLS carries which protocol

TransportMay carry
TLS 1.3ISO 15118-20 and ISO 15118-2
TLS 1.2ISO 15118-2
TLS 1.1 or olderISO 15118-2 with external identification (EIM) only
No TLSISO 15118-2 with EIM, and DIN SPEC 70121

From Table 5. A car must not offer ISO 15118-20 in supportedAppProtocolReq on a connection that is not TLS 1.3 (V2G20-1237), and a charger must not select it (V2G20-2356). Bench captures often switch TLS off so the messages stay readable; HS-03 reports that as a warning.

The handshake the car sends (ClientHello)

  • The car is always the TLS client and the charger the server (V2G20-2362, V2G20-2374).
  • supported_versions contains TLS 1.3 (0x0304); legacy_version stays 0x0303 as RFC 8446 requires (V2G20-2364, V2G20-2365). A car that also speaks ISO 15118-2 adds TLS 1.2 and lists the TLS 1.2 suites after the TLS 1.3 ones (V2G20-2058, V2G20-2062).
  • Cipher suites of Table 6: TLS_AES_256_GCM_SHA384 and TLS_CHACHA20_POLY1305_SHA256 (V2G20-2459).
  • Named groups of Table 7: secp521r1 and x448, with a key share for them (V2G20-1637, V2G20-1663).
  • Signature algorithms of Table 8: ecdsa_secp521r1_sha512 and ed448 (V2G20-1669).
  • status_request with an empty responder_id_list, so the charger staples OCSP responses (V2G20-2372, V2G20-2373).
  • certificate_authorities with the V2G root CAs the car trusts, empty in pairing mode for private chargers (V2G20-1006).
  • No early_data: 0-RTT is not allowed, and a pre-shared key is only for resuming a session (V2G20-1612, V2G20-2021).

TL-05 checks all of these, one finding per requirement. A car that leaves TLS 1.3 out asks for ISO 15118-2 over TLS 1.2 (V2G20-2063), and TL-05 does not apply to it.

What the charger answers (ServerHello)

  • The charger supports every suite and group of Tables 6 and 7, so it has to take the car's most preferred one (V2G20-1857, V2G20-2460).
  • The chosen group appears in the key_share of the ServerHello (V2G20-1665).
  • The charger sends its certificate chain up to, but not including, a root the car named (V2G20-1007, V2G20-2399), with OCSP responses for each certificate, and asks for the vehicle certificate (V2G20-2400).

In TLS 1.3 everything after the ServerHello is encrypted, including both certificate chains. TL-06 checks the ServerHello; PK-01 and PK-02 can only read certificates in TLS 1.2 captures.

Field experience

  • Certificates grow from about 800 bytes in ISO 15118-2 to about 1600 bytes. Memory and run time on small controllers need checking early.
  • Certificates with the wrong time format (GeneralizedTime before 2050) and unexpected critical extensions are a common cause of failed handshakes. PK-02 checks both in TLS 1.2 chains.
  • On the public example captures, one bench EV emulator sends neither status_request nor certificate_authorities, and one open source stack negotiates secp256r1, which Table 7 does not allow.

Reading an encrypted session

Without the session keys the tool can only report "Encrypted, not decrypted" and check the handshake. Add the TLS key log (the SSLKEYLOGFILE format) that one of the two stacks exported, and the tool decrypts the session and checks its messages like any other; see TLS in charging captures.

Sources

  • ISO 15118-20:2022, TLS and certificate requirements, Tables 5 to 9
  • RFC 8446, TLS 1.3