Discussion
Post-quantum crypto is not green: more RAM and CPU is necessary (ML-DSA eats a lot of memory). How to adapt PQ crypto to constrained devices? https://datatracker.ietf.org/doc/draft-ietf-pquip-pqc-hsm-constrained/
Among the ideas: if you have CPU but not RAM, store only the seed and regenerate keys on the fly.
Now, regext, the protocols for the domain name industry (except RPP which is too new and has its own group). #EPP#RDAP #whois (just kidding)
https://datatracker.ietf.org/meeting/123/materials/agenda-123-regext-04
Among the issues: should JScontact replace jCard in RDAP or just be an experimental alternative?
Bare identifiers-without a prefix "extension_") in RDAP extensions? Hot topic.
RFC erratum https://www.rfc-editor.org/errata/eid8305 is interesting because it is an example of the free-form (natural language) and formal schema in a #RFC saying different things.
And now, since we have to do something against the Quantum Apocalypse, the pquip working group: post-quantum crypto in protocols. https://datatracker.ietf.org/meeting/123/materials/agenda-123-pquip-04
The first #RFC of the group, 9794 (terminology for hybrid schemes), has just been published. Soon, the RFC "PQ crypto for engineers" (introduction and explanations) is almost ready.
Post-quantum crypto is not green: more RAM and CPU is necessary (ML-DSA eats a lot of memory). How to adapt PQ crypto to constrained devices? https://datatracker.ietf.org/doc/draft-ietf-pquip-pqc-hsm-constrained/
Among the ideas: if you have CPU but not RAM, store only the seed and regenerate keys on the fly.
A space for Bonfire maintainers and contributors to communicate
