Minutes of the July 2nd, 2024 Meeting:

[johngray-dev]

Participants:

Pala, Massimiliano
Brockhaus, Hendrik (T CST SEA-...
Carl Wallace (Guest) (Digicert)
Daniel Van Geest (Unverified)
David Hook (KeyFactor)
Felipe Ventura (Entrust)
John Gray (Entrust)
Julien Prat (Crypto Next)
Klaußner, Jan (Unverified)
Markku-Juhani O. Sa... () &
Mike Ounsworth (Entrust)
Petr Muzikant (Cyber) (Unverified)
Railean, Alexander (T CST SEA-D...
Tomofumi Okubo (DigiCert)

Meeting Outline:

• The meeting started with the discussion about OIDs and the need to align them across implementations. The .999 is used today (experimental), but we should move away from that now and get non-experimental OIDs.
• As soon as the official OIDs are assigned to the PQC algorithm, implementations must update the support for it.
• We briefly discussed the release of the ACVP server (GitHub - usnistgov/ACVP-Server: A repository tracking releases of NIST's ACVP server. See www.github.com/usnistgov/ACVP for the protocol.)
• Markku is going to post the python wrapper for NIST golden reference in C# in the pqc-forum list. The python wrapper should make it easier to integrate/use.
• David to produce Encrypted Data via standard CMS with KEM recipient using Kyber with bouncycastle (Strange check in org.bouncycastle.asn1.cms.KEMRecipientInfo.KEMRecipientInfo(ASN1Sequence) · Issue #1665 · bcgit/bc-java · GitHub)
• Mike to work on the updated version of the Interoperability matrix (v4) and automate it via GitHub actions.
• The CMS Interoperability results are available here: ietf-hackathon.github.io/pqc-certificates/pqc_hackathon_results_cms_v1.html
• Carl Wallace shared the KEMRI (Kem Recipient Info) implementation that is available here: GitHub - carl-wallace/kemri_toy: Test gadget for working with the new KEMRecipientInfo structure
• The team is planning for the needed work for the next IETF hackathon. It seems that many of the team will participate remotely to both IETF and Hackathon – we will be using Gather (as usual – Table G) if it is still available. Otherwise we might organize for an open Teams Session for the Hackathon discussion/help/cooperation.