Éric Vyncke has entered the following ballot position for draft-ietf-cose-tsa-tst-header-parameter-05: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-cose-tsa-tst-header-parameter/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-cose-tsa-tst-header-parameter-05 CC @evyncke Thank you for the work put into this document. Please find below some non-blocking COMMENT points. Special thanks to Michael Jones for the shepherd's write-up including the WG consensus but the justification of the intended status is rather light. Other thanks to Alexey Melnikov, the IoT directorate reviewer (at my request), please consider this int-dir review: https://datatracker.ietf.org/doc/review-ietf-cose-tsa-tst-header-parameter-05-iotdir-telechat-melnikov-2025-04-30/ (and I have read Thomas' reply) I hope that this review helps to improve the document, Regards, -éric ## COMMENTS (non-blocking) ### Fit the COSE charter ? I support Roman's DISCUSS on this I-D not fitting the COSE charter. ### Section 1.1 Please expand "TSA" at first use. Add reference(s) for TSA (RFC 3161 ?) & "Transparency Service". ### Section 2 Isn't 'boxes' unclear in `by allowing multiple private-key boxes` ? ### Section 2.1 Thanks for using SVG graphics, much cleaner. Should clock also be considered as input in the TSA box in figure 1 ? The graphics seems to indicate that the private key is feeded in the clock... _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
