Re-assign all code points

[baentsch]

As correctly questioned in #556 (comment) the code points in this project are not aligned with IANA, most notably code points from non-standardized algorithms are not in the "Reserved for private use" space.

This issue is to suggest changing that -- ideally in a long-term easily maintainable manner, best fully automatic during algorithm changes done to the underlying liboqs.

[pi-314159]

Talking about resigning codepoints: Since Chrome 131 was released today (Edge 131 this Thursday) and Firefox 132 was released on October 29, we can drop Kyber support. Additionally, to simplify maintenance efforts, we can reverse the order of all X25519 hybrids.

I suggest doing this with the liboqs 0.12.0 or 1.0 release.

@baentsch @bhess

[baentsch]

Following the mantra "less code is more secure code" I'm all for simplification and easing maintenance and would be OK dropping all Kyber support (incl. "hybrid order juggling") for good (also making the implementation effort for this issue quicker). Objections, @dstebila @SWilson4 ?

[dstebila]

I've created open-quantum-safe/liboqs#1989 about dropping Kyber support.

[baentsch]

Another code point proposal to track/implement: https://datatracker.ietf.org/doc/html/draft-tls-westerbaan-mldsa-00

[tomato42]

I think that ML-DSA codepoints are especially important, so I've filed #578 to track them.

[baentsch]

I think that ML-DSA codepoints are especially important, so I've filed #578 to track them.

Well, this doesn't really fit this issue: Adapting the ML-DSA code points and OIDs is run-of-the-mill business that has nothing to do with the "general overhaul" (beyond non-standardized IDs) that this issue suggests: As the code base gets updated to actually include the standardized code (in this case, as per #568) the corresponding code points (and OIDs) get updated. That said, your issue really should be a PR feedback... Just used it that way :)

[tomato42]

@baentsch aah, I took #561 (comment) as you wanting to use this issue for cleanup in general, sorry about that 🙂

will take a look at #568

[baentsch]

@baentsch aah, I took #561 (comment) as you wanting to use this issue for cleanup in general, sorry about that 🙂

I wouldn't want to clean up things that are not even available for tidying :-)

will take a look at #568

Thanks.