Hi! Unfortunately, we couldn't submit the draft before the meeting and discuss it face-to-face.
But here's a -01 fresh from the oven. We absorbed the feedback we got in SF and went ahead with one single header. However, the two modes of use ([1], [2]) define different inputs into the timestamping machinery and therefore create a different binding between COSE and TST. At present, the only way to distinguish between the two semantics is by their position in the COSE message (i.e., protected vs unprotected), which does not look like a good design :-) cheers, thanks [1] https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-01.html#section-2.1 [2] https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-01.html#section-2.2 ---------- Forwarded message --------- From: <[email protected]> Date: Tue, 7 Nov 2023 at 14:36 Subject: New Version Notification for draft-ietf-cose-tsa-tst-header-parameter-01.txt To: Henk Birkholz <[email protected]>, Maik Riechert <[email protected]>, Maik Riechert <[email protected]>, Thomas Fossati <[email protected]>, <[email protected]> A new version of Internet-Draft draft-ietf-cose-tsa-tst-header-parameter-01.txt has been successfully submitted by Thomas Fossati and posted to the IETF repository. Name: draft-ietf-cose-tsa-tst-header-parameter Revision: 01 Title: COSE Header parameter for RFC 3161 Time-Stamp Tokens Date: 2023-11-07 Group: cose Pages: 6 URL: https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-01.txt Status: https://datatracker.ietf.org/doc/draft-ietf-cose-tsa-tst-header-parameter/ HTML: https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-01.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-cose-tsa-tst-header-parameter Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-tsa-tst-header-parameter-01 Abstract: RFC 3161 provides a method for timestamping a message digest to prove that the message was created before a given time. This document defines a CBOR Signing And Encrypted (COSE) header parameter that can be used to combine COSE message structures used for signing (i.e., COSE_Sign and COSE_Sign1) with existing RFC 3161-based timestamping infrastructure. The IETF Secretariat _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
