[Chair hat on]


There's no mystery as to what it would take to add SHA-3 functions to 
https://www.iana.org/assignments/cose/cose.xhtml#algorithms.  Write a draft 
that performs the wanted IANA registrations.  Targeted drafts with a limited, 
specific purpose are easy to write.



I'll note that my co-chair sent the call for agenda items for IETF 123 out on 
Tuesday.  See "IETF 123 Call for COSE Agenda Items".  Respond to it if you want 
to discuss your draft at IETF 123.



Be sure to submit your draft by the Monday, July 7 submission 
deadline<https://datatracker.ietf.org/meeting/important-dates/#IETF123>.



                                                       Best wishes,

                                                       -- Mike



-----Original Message-----
From: Carsten Bormann <[email protected]>
Sent: Thursday, June 26, 2025 8:03 AM
To: Quynh Dang <[email protected]>
Cc: Sipos, Brian J. <[email protected]>; [email protected]; Leonard Rosenthol 
<[email protected]>
Subject: [COSE] Re: Why is SHA-3 not supported in COSE?



On 2025-06-26, at 16:11, Quynh Dang 
<[email protected]<mailto:[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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc8152%23section-16.4&data=05%7C02%7C%7C88a54538602243db7c2408ddb4c28a40%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638865469818955982%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1UWeynz6MVQU2KDSZaqY5cE1PngCTdpV%2B0mk61UF2S0%3D&reserved=0<https://www.rfc-editor.org/rfc/rfc8152#section-16.4>



_______________________________________________

COSE mailing list -- [email protected]<mailto:[email protected]>

To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to