Hi,

This version (-03) should address all comments we received during WGLC.

A big thank you to all who provided feedback and contributed prose and pictures.

We believe we were diligent in processing your input, but please
double-check that that's the case [1].

cheers!

On Tue, 10 Sept 2024 at 15:58, <[email protected]> wrote:
>
> Internet-Draft draft-ietf-cose-tsa-tst-header-parameter-03.txt is now
> available. It is a work item of the CBOR Object Signing and Encryption (COSE)
> WG of the IETF.
>
>    Title:   COSE Header parameter for RFC 3161 Time-Stamp Tokens
>    Authors: Henk Birkholz
>             Thomas Fossati
>             Maik Riechert
>    Name:    draft-ietf-cose-tsa-tst-header-parameter-03.txt
>    Pages:   10
>    Dates:   2024-09-10
>
> Abstract:
>
>    This document defines a CBOR Signing And Encrypted (COSE) header
>    parameter 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.
>
> Discussion Venues
>
>    This note is to be removed before publishing as an RFC.
>
>    Source for this draft and an issue tracker can be found at
>    https://github.com/ietf-scitt/draft-birkholz-cose-tsa-tst-header-
>    parameter.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-cose-tsa-tst-header-parameter/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-cose-tsa-tst-header-parameter-03.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-tsa-tst-header-parameter-03
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> 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