On 2025-06-26, at 16:11, Quynh Dang <[email protected]> wrote:
>
> If the chairs make an adoption call, I would support it and below would be
> additional input to be considered for the draft.
If somebody actually writes the draft to be adopted here (with the additional
Hash/XOF and the MACs), we don’t need a separate activity to get the comment
about SHA-3 in place — this could just be part of the IANA considerations of
this draft.
This, of course, assumes that we can do this in finite time; otherwise, having
a very short separate draft (which doesn’t even have to be published as an RFC)
with just the SHA-3 comment could speed up making the registry less confusing.
Note that the template for making a new COSE algorithm registration [1]
includes providing a value for the Recommended column:
Recommended: Does the IETF have a consensus recommendation to use
the algorithm? The legal values are 'Yes', 'No', and
'Deprecated'.
That is currently “no” for TurboSHAKE/kangarootwelve, if only because these
registrations are provided defined by an IRTF document; we *could* upgrade this
to “yes”.
Grüße, Carsten
[1]: https://www.rfc-editor.org/rfc/rfc8152#section-16.4
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
