The draft looks good to me. I have two minor suggestions. 

 

In section 3.2, there is language about minimizing dependencies by using the 
same hash for the timestamp and the signature. This suggestion does not seem to 
be unique to CTT, so I’d either repeat the language in 3.1 or move the language 
to a more general location that covers both use cases.

 

In section 4, I suggest changing 

 

“the receiver MUST make sure that the message imprint in the embedded timestamp 
token matches either the payload or the signature fields, depending on the mode 
of use”

 

to something like

 

“the receiver MUST make sure that the message imprint in the embedded timestamp 
token matches a hash of the payload, signature, or signatures field, depending 
on the mode of use and type of COSE structure”

 

 

 

From: Michael Jones <[email protected]>
Date: Tuesday, July 30, 2024 at 1:53 PM
To: "[email protected]" <[email protected]>
Subject: [COSE] WGLC for draft-ietf-cose-tsa-tst-header-parameter

 

Hi all,

 

This message starts the Working Group Last Call (WGLC) for 
https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-02.html.
  The WGLC will run for two weeks, ending on Tuesday, August 13, 2024.

 

Please review and send any comments or feedback to the working group.  Even if 
your feedback is “this is ready for publication”, please let us know.

 

                                                       Thank you,

                                         -- Mike and Ivaylo, COSE Chairs

 

_______________________________________________ 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]

Reply via email to