[openpgp] Re: I-D Action: draft-ietf-openpgp-nist-bp-comp- 00.txt
Simon Josefsson <[email protected]>
| Newsgroups | gmane.ietf.openpgp |
|---|---|
| Message-ID | <[email protected]> |
I like that this document moves NIST/BSI curves out from the main document, and also that they target the MAY level, so +1 since I think we need more PQ hyrid options around. I wish that PGP would use a CFRG-aligned PQ/T combiner, but I also believe CFRG has proven itself not worthy to wait for guidance on this matter. While I prefer the Chempat combiner I think it is reasonable to proceed with a custom PGP-specific combiner here. I also found alignment of MLKEM768 with P384 and brainpoolP256 surprising, but I don't care strongly about that. /Simon Falko Strenzke <[email protected]> writes: > After the adoption of draft-ietf-openpgp-nist-bp-comp, we would like > to initiate the discussion about the code points. The draft currently > has > > 5 for encryption: > > ML-KEM-512+ECDH-NIST-P-256 MAY > ML-KEM-768+ECDH-NIST-P-384 MAY > ML-KEM-1024+ECDH-NIST-P-384 MAY > ML-KEM-768+ECDH-brainpoolP256r1 MAY > ML-KEM-1024+ECDH-brainpoolP384r1 MAY > > 5 for signature: > > ML-DSA-44+ECDSA-NIST-P-256 MAY > ML-DSA-65+ECDSA-NIST-P-384 MAY > ML-DSA-87+ECDSA-NIST-P-384 MAY > ML-DSA-65+ECDSA-brainpoolP256r1 MAY > ML-DSA-87+ECDSA-brainpoolP384r1 MAY > > Please respond on the list whether you agree or disagree with these > sets. Questions or discussions about the motivations etc. are of > course also welcome. > > @Chairs: Can we plan a slot at the end of the interim next week to > discuss the code points? > > That being said, I also encourage the WG to read the draft in > general. Since it is fully aligned with draft-ietf-openpgp-pqc, the > potential for discussions is probably low. The code points are > presumably the main discussion point. Once the code points have been > agreed on, the draft can probably progress quickly. > > If you want to review the draft, I suggest to wait until version 01, > as we are currently in the process of applying the latest relevant > editorial changes that have been made to draft-ietf-openpgp-pqc. > > Falko > > Am 09.10.25 um 16:18 schrieb [email protected]: >> Internet-Draft draft-ietf-openpgp-nist-bp-comp-00.txt is now available. It is >> a work item of the Open Specification for Pretty Good Privacy (OPENPGP) WG of >> the IETF. >> >> Title: PQ/T Composite Schemes for OpenPGP using NIST and Brainpool Elliptic Curve Domain Parameters >> Authors: Quynh Dang >> Stephan Ehlen >> Stavros Kousidis >> Johannes Roth >> Falko Strenzke >> Name: draft-ietf-openpgp-nist-bp-comp-00.txt >> Pages: 29 >> Dates: 2025-10-09 >> >> Abstract: >> >> This document defines PQ/T composite schemes based on ML-KEM and ML- >> DSA combined with ECDH and ECDSA algorithms using the NIST and >> Brainpool domain parameters for the OpenPGP protocol. >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-openpgp-nist-bp-comp/ >> >> There is also an HTML version available at: >> https://www.ietf.org/archive/id/draft-ietf-openpgp-nist-bp-comp-00.html >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> openpgp mailing list [email protected] >> To unsubscribe send an email [email protected] _______________________________________________ openpgp mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 1.2 KB)
-----BEGIN PGP SIGNATURE----- iQNoBAEWCAMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmjqPjMUHHNpbW9uQGpv c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh BLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XQkBQkNZGbwAAoJENc89jjFPAa+BtIA /iR73CfBurG9y8pASh3cbGOMHpDZfMAtosu6jbpO69GHAP4p7l57d+iVty2VQMsx +3TCSAvZkpr4P/FuTzZ8JZe8BrgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0 +MTXPPY4xTwGvgUCZ9F0SgUJDWRmSQCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE 8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J ENc89jjFPAa+wUUBAO64fbZek6FPlRK0DrlWsrjCXuLi6PUxyzCAY6lG2nhUAQC6 qobB9mkZlZ0qihy1x4JRtflqFcqqT9n7iUZkCDIiDbg4BFySz2oSCisGAQQBl1UB BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XTSBQkNZGboAAoJENc89jjF PAa+0M0BAPPRq73kLnHYNDMniVBOzUdi2XeF32idjEWWfjvyIJUOAP4wZ+ALxIeh is3Uw2BzGZE6ttXQ2Q+DeCJO3TPpIqaXDAAKCRBRcisI/kdFokHgAP9nk3MX3hVW aLbiKliOrwblNeeBDNnIGPHsv1/wA2qBxgD+O0fb6/3O1qKuEEQLNsar+x/suR7x /IwKkGBMaKKoBAs= =sq2C -----END PGP SIGNATURE-----