This draft was on the agenda in Shenzhen but for some reason no presentation
was made. That would have been the easiest way to get feedback on the draft.
At this point, I suggest that you address Christian Amsüss' review comments and
publish another draft. At that point the next step would be to get several
reviews of the draft and see what they say.
Best wishes,
-- Mike
-----Original Message-----
From: Dmytro OCHKAS <[email protected]>
Sent: Monday, March 16, 2026 3:42 AM
To: cose <[email protected]>
Subject: [COSE] New version of draft-ochkas-cose-ascon
Dear COSE WG,
I am allowing myself to relaunch the conversation on adopting Ascon over COSE.
In our team, we are still very interested in this idea, and we think it could
be a great and meaningful contribution to the COSE standard.
After IETF 123 Madrid, where it was warmly welcomed, the draft underwent
several major improvements, including:
1. Three variations of Ascon-AEAD128 for COSE with 128-, 64-, and 32-bit tags
correspondingly.
2. Two variations of Ascon-AEAD128 for JOSE with 128-, 64-bit tags.
3. The examples for COSE and JOSE with Ascon-AEAD128 with our implemented
libraries.
We find it important to have a 32-bit Ascon tag option in COSE for extremely
constrained use-cases, including the securization of underwater, satellite, and
ambient IoT networks.
But, in the draft, Ascon with the 32-bit tag is marked "Filter Only" to prevent
its use without an adequate risk analysis.
We would also like to know if there is an interest in introducing Ascon-Hash256
over COSE.
In the meantime, we are going to prepare the next version of the draft,
including Ascon-Hash256 over COSE.
We count on the interest in the WG to work on the idea together and are open to
any remarks/questions.
Best regards,
Dmytro Ochkas
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
