Minutes of the August 29th 2023 Meeting

[johngray-dev]

Notes from August 29th 2023:

Present: John G, Mike O, Markku O, Max P, Christoph W, Robert H, Corey B, David H, Alexander R, Felipe

• Two new members joined the team: Christoph Wildfeuer and Robert Hulshof
• Discussed and subsequently updated the OID Mapping table to align with the NIST standards released last week: https://github.com/IETF-Hackathon/pqc-certificates/blob/master/docs/oid_mapping.md
  • Decided to keep using the names Dilithium, SPHINCS+ and Kyber to differentiate between the prototype OIDs we have specified and whatever will become the final OIDs
• Discussed the proposed artifact R3 .zip file format in Added the R3 artifacts zip format #69 . We all agreed to this new format to simplify basic interoperability with the algorithms.
  • Mike Ounsworth made some tweaks to the format based on the discussion
  • We decided to rename artifact files to _certs.zip or _cms.zip, etc. Essentially we will specify simple .zip file formats for the type of item we will test going forward. For now we are focusing on the basic certificate and signature tests
  • For Kyber certs we use EE certs signed by the Dilithium trust anchors (since Kyber is not a signing algorithm).
  • For Hybrid (composite, catalyst, Delta, multi auth or others), we will use these 3 combinations:
    • RSA_3072(SHA256)+Dilithium2 (security level 128 bits)
    • ECDSA_P256(SHA256)+Dilithium2 (security level 128 bits)
    • ECDSA_P521(SHA512)+Dilithium5 (security level 256 bits)
• Discussed updating the compatibility matrix tooling based on the simplified .zip file format
  • We decided to keep this here for legacy information: https://ietf-hackathon.github.io/pqc-certificates/pqc_hackathon_results.html
  • We will create an update matrix based on the draft algorithm prototype OIDS and simplified combinations as specified above. This will give better baseline interoperability results.
• We discussed having a Virtual Interim Hackathon on Saturday September 30th.
  Action: John to send an e-mail out to the hackathon team to see if there is interest