Offering oqsprovider for IETF X.509 hackathon?

[baentsch]

Here's the original proposal from the pqc mailing list:

We are suggesting to play with Dilithium, Falcon, Sphincs+, and
Composite signing algorithms in Certs, CRLs, CSRs, PKCS#12s, CMS
SignedData, maybe OCSP Responses, maybe Timestamping, maybe CMP. We can
bring: the Entrust Toolkit (which we
can hack at), Bounce Castle, OpenQuantumSafe-openssl, OpenCA (easier if
Max Pala is there, but we can probably figure out how to build it).

Question 2: whether or not you're joining, what PQ X.509 / PKIX things
would you like to see working with Dilithium, Falcon, Sphincs+,
Composite?

Would it be worth while also suggesting oqsprovider as another piece of software for this hackathon?

I don't want to replace oqs-openssl as already suggested above, though, as the team writing the suggestion above seems to be already familiar with it. Also, I personally have not participated in such IETF event and don't know what that would get us (me?) into. Whatever, I'd think oqsprovider is reasonably straightforward to adapt (with open-quantum-safe/oqs-provider#77 it's now even possible to set X.509 OIDs by env var) -- within the confines of OpenSSL, of course. Opinions?