Hi Alexey, On Wed, 30 Apr 2025 at 17:20, Alexey Melnikov via Datatracker <[email protected]> wrote: > > Document: draft-ietf-cose-tsa-tst-header-parameter > Title: COSE Header parameter for RFC 3161 Time-Stamp Tokens > Reviewer: Alexey Melnikov > Review result: Ready > > Hi, > > I am the assigned IoT-Directorate reviewer for this draft. > > Summary: Ready. > > This document defines two CBOR Signing And Encrypted (COSE) header > parameters for incorporating RFC 3161-based timestamping into COSE > message structures (COSE_Sign and COSE_Sign1). This enables the use > of established RFC 3161 timestamping infrastructure to prove the > creation time of a message. > > While I think it might be a bit of an ask for an IoT implementation > to implement both COSE based processing and X.509 based processing, > if the IoT implementation has code for both, this would be a reasonable > way to combine them.
I'd expect 7228bis C4 and upwards to have enough memory and processing capabilities. But yes, not all constrained nodes will be able to ship with the required code. Because the content of these headers tends to be quite hefty, another aspect to consider is how constrained the network is: I guess the typical LLN will sweat carriyng one of these :-) > I think the document is well written and clear. Thanks very much for reviewing it. cheers! _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
