> Tangentially, this is registering a `NamedGroup` / `SupportedGroup`, but of course it's not a group, it's a KEM scheme over which no Diffie-Hellman of any kind can be done. Where do IANA preallocations start bumping up against "well we're doing something completely different anyway"?
The deciding factor for these registries isn't the names of the fields but what the protocol does with them. If we started a new registry for KEMs, it wouldn't be useful in TLS because TLS 1.3 specifically needs a codepoint in the NamedGroup enum. The FFDH range isn't treated special because of naming but because of some mistakes that RFC 7919 made where the implementation actually needs to categorize codepoints. The group naming is unfortunate but the last ill-advised rename from curve to group was incredibly expensive. If we want to rename it again, "KEM" or "KeyAgreement" or "KeyExchange" or "KeyShareType" would have been a much better name, but given how problematic the last rename was, I'm not very thrilled about the prospect. See also https://mailarchive.ietf.org/arch/msg/tls/-jYbYd7cXKIzySPp578kAsWZt5c/ David On Fri, Nov 1, 2024 at 12:28 PM Deirdre Connolly <durumcrustu...@gmail.com> wrote: > If there's a choice to be made I favor the 512 513 514 choices > > On Fri, Nov 1, 2024, 12:20 PM Deirdre Connolly <durumcrustu...@gmail.com> > wrote: > >> Ah, oops! >> >> Tangentially, this is registering a `NamedGroup` / `SupportedGroup`, but >> of course it's not a group, it's a KEM scheme over which no Diffie-Hellman >> of any kind can be done. Where do IANA preallocations start bumping up >> against "well we're doing something completely different anyway"? >> >> >> On Fri, Nov 1, 2024, 11:47 AM Salz, Rich <rs...@akamai.com> wrote: >> >>> I made a mistake and you're right " 261, 262, and 263 are assigne to the >>> MLKEM512, MLKEM768, and MLKEM1024" wrong. >>> >>> We'll notify IANA to pick 512 513 514 or 4584 4585 4586. Or something. >>> >>> _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-le...@ietf.org >
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
