Re: [lamps] [EXTERNAL] Current efforts in the direction of draft-truskovsky-lamps-pq-hybrid-x509?

[John Gray <[e-mail]>]

Iyán,

This is interesting timing,

Corey's message earlier today introduced our new draft, which is a slightly different approach to the Hybrid Catalyst problem:
https://datatracker.ietf.org/doc/draft-bonnell-lamps-chameleon-certs/   I copied his message below:

Cheers,

John Gray


From: Spasm <[e-mail]> On Behalf Of Corey Bonnell
Sent: Friday, July 7, 2023 8:11 AM
To: LAMPS WG <[e-mail]>
Subject: [EXTERNAL] [lamps] A Mechanism for Encoding Differences in Paired Certificates ("Chameleon Certificates")

Hello,
At the Hackathon at IETF 116 this March, several participants implemented the “Hybrid Catalyst” certificate extension processing initially documented in https://datatracker.ietf.org/doc/html/draft-truskovsky-lamps-pq-hybrid-x509-01 and later standardized in ITU-T X.509 10/2019. This implementation experience led several of us to explore alternative mechanisms to efficiently convey multiple keys and other attributes in a single X.509 certificate. The product of these discussions is the specification a mechanism informally called “Chameleon Certificates” at https://datatracker.ietf.org/doc/draft-bonnell-lamps-chameleon-certs/. The mechanism that we developed allows for the differences between two related certificates to be encoded in a single extension within one of the certificates. Relying parties can then extract the other certificate using the information found in the extension.

The primary use case in mind is algorithm migration, in particular post-quantum algorithm migration. However, the mechanism can also be applied to other use cases, such as efficiently encoding a signing certificate and encryption certificate in one X.509 certificate.

Several folks are already planning to work on implementing this draft at the IETF 117 Hackathon, but we’d like to circulate this draft to this group for initial thoughts.

Thanks,
Corey on behalf of the authors

-----Original Message-----
From: Spasm <[e-mail]> On Behalf Of Iyán Méndez Veiga
Sent: Friday, July 7, 2023 10:05 AM
To: [e-mail]
Subject: [EXTERNAL] [lamps] Current efforts in the direction of draft-truskovsky-lamps-pq-hybrid-x509?

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.

______________________________________________________________________
Hello,

I recently found the interesting draft-truskovsky-lamps-pq-hybrid-x509, which I think it would allow a much smoother PQC transition.

Unfortunately, the draft has expired some time ago, and I couldn't find any derivative work apart from a small reference by Mike that this was standardized by ITU-T [1]. I guess he was referring to section 7.2.2 of their
X.509 (10/2019):

https://urldefense.com/v3/__https://www.itu.int/rec/T-REC-X.509-201910-I__;!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYA72a7Cv$

There was also some recent mention to the draft in the IETF 116 Hackathon "PQ Use in the Read world: X.509 Keys, signatures, certificates and protocols", but I couldn't find any details.

It was also pointed out to me [2] that this approach was protected by a patent owned by ISARA, but later it seems they relaxed this restriction [3].

DigiCert seems to be testing this idea as well [4].

Could anyone summarize to me the current status of this work? Why this draft never got updated? Are there any plans to continue working on this with an active draft?

People from the Open Quantum Safe project have shown interest in implementing this, since it's a good approach with a straightforward backwards compatibility, but since changes have to be made to OpenSSL as well, and I quote here "not having this at least in active Draft state at IETF makes this a non-starter".

Looking forward to learning more about the status of this work.

Best regards,
Iyán

[1]: https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/spasm/VJPJXLquDjEjEmRysiGrdsL-Nwc/__;!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYNGV1vCo$
[2]: https://urldefense.com/v3/__https://github.com/open-quantum-safe/oqs-provider/discussions/209__;!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYJUx_S7u$
[3]: https://urldefense.com/v3/__https://www.helpnetsecurity.com/2022/10/26/isara-digital-certificate-patents-quantum-security/__;!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYLKSruV6$
[4]: https://urldefense.com/v3/__https://docs.digicert.com/en/certcentral/certificate-tools/post-quantum-cryptography.html*idm45907393047856__;Iw!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYATBKYee$


_______________________________________________
Spasm mailing list
[e-mail]
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/spasm__;!!FJ-Y8qCqXTj2!dNyWih2XJr-B63kAzEaisQuaTWxwCy2LkamjW-v6YwOHAh1Gv22KC4xXwQtjjjiRUbt7XXRymy4Jd71PYIiMMklq$
Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.