Hi all,

Before I go on holiday and forget who I am once again: Please note
that once the IANA has assigned the final code points, we will need to
recalculate the examples.

This process is fully automated and should only take a couple of
minutes, but we should still flag it somehow to avoid surprising
people.

cheers, t

On Fri, 18 Jul 2025 at 12:13, Michael Jones <[email protected]> wrote:
>
> I have requested publication of the specification.
>
>                                 -- Mike
>
> -----Original Message-----
> From: Thomas Fossati <[email protected]>
> Sent: Thursday, June 12, 2025 12:41 PM
> To: [email protected]; The IESG <[email protected]>
> Cc: Deb Cooley <[email protected]>; Stefan Santesson <[email protected]>
> Subject: [COSE] Re: I-D Action: 
> draft-ietf-cose-tsa-tst-header-parameter-06.txt
>
> Hi, all,
>
> This version should address the IESG feedback (including Stefan Santesson's 
> secdir review).
>
> The exec summary:
> 1. Swapped presentation of the headers (CTT first, TCC second) 2. Reworked 
> the use cases section 3. Added warning text for implementers suggested by 
> Stefan 4. Some minor clarifications coming from different IESG reviewers
>
> For the details, see the diff below.
>
> Thanks very much for your patience.
>
> cheers!
>
> On Thu, 12 Jun 2025 at 12:30, <[email protected]> wrote:
> >
> > Internet-Draft draft-ietf-cose-tsa-tst-header-parameter-06.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-06.txt
> >    Pages:   25
> >    Dates:   2025-06-12
> >
> > Abstract:
> >
> >    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 in COSE-based
> >    protocols.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datat/
> > racker.ietf.org%2Fdoc%2Fdraft-ietf-cose-tsa-tst-header-parameter%2F&da
> > ta=05%7C02%7C%7C8be5980dec914a3ce99b08dda99dab61%7C84df9e7fe9f640afb43
> > 5aaaaaaaaaaaa%7C1%7C0%7C638853216844018157%7CUnknown%7CTWFpbGZsb3d8eyJ
> > FbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpb
> > CIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=k%2F0usrDiI6TSRLy5kS9dAgIFc5wJC
> > fRHlEmnaxJoGoc%3D&reserved=0
> >
> > There is also an HTML version available at:
> > https://www.i/
> > etf.org%2Farchive%2Fid%2Fdraft-ietf-cose-tsa-tst-header-parameter-06.h
> > tml&data=05%7C02%7C%7C8be5980dec914a3ce99b08dda99dab61%7C84df9e7fe9f64
> > 0afb435aaaaaaaaaaaa%7C1%7C0%7C638853216844047915%7CUnknown%7CTWFpbGZsb
> > 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjo
> > iTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ponzi1LZ6svKgftUg%2FFpO6p
> > SnhXrJF7E%2Bx4qbCzqRB0%3D&reserved=0
> >
> > A diff from the previous version is available at:
> > https://autho/
> > r-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-cose-tsa-tst-header-para
> > meter-06&data=05%7C02%7C%7C8be5980dec914a3ce99b08dda99dab61%7C84df9e7f
> > e9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638853216844070742%7CUnknown%7CTWFp
> > bGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIk
> > FOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kY2rMcu3h7%2B4ZRfWVE
> > hGmvQB%2Btw2csXx2O9OhLrUVaE%3D&reserved=0
> >
> > 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]

_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to