With the incorporation of the previous feedback already provided on this draft, Iβm a +1 to this document. Itβs a highly useful feature as the draft cites from JWT that I can see similar applications for with COSE structures.
Thanks, [MATTR website]<https://mattr.global/> Tobias Looker MATTR +64 273 780 461 [email protected]<mailto:[email protected]> [MATTR website]<https://mattr.global/> [MATTR on LinkedIn]<https://www.linkedin.com/company/mattrglobal> [MATTR on Twitter]<https://twitter.com/mattrglobal> [MATTR on Github]<https://github.com/mattrglobal> This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it β please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. From: COSE <[email protected]> on behalf of Henk Birkholz <[email protected]> Date: Thursday, 23 November 2023 at 8:32β―AM To: Ivaylo Petrov <[email protected]>, Cose Chairs Wg <[email protected]>, cose <[email protected]> Subject: Re: [COSE] π WGLC of draft-ietf-cose-typ-header-parameter EXTERNAL EMAIL: This email originated outside of our organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe. +1 I've read the I-D previously and after skimming it again and all I can find is one minor nit: The terms "COSE object", "object" are used synonymously. Without being familiar with JOSE (or maybe COSE in general) it is not crystal clear, if you mean COSE envelope including payload ("COSE object") or just playload ("object"). This is a very minor nit. I assume it would probably never be confused with just payload and very rarely be confused with different application specific types of payloads that share the same content format (not including the COSE envelope). In general, this work is quite complementary to profiling COSE headers in general and pulling it in from JOSE is a very convenient step towards that goal. Viele GrΓΌΓe, Henk On 15.11.23 22:40, Ivaylo Petrov wrote: > Dear all, > > As discussed during IETF 118, this message starts the formal Working > Group Last Call of the draft-ietf-cose-typ-header-parameters-in-headers [1]. > > The working group last call will run for **three weeks** (due to > thanksgiving), ending on Dec 6, 2023. > > Please review and send any comments or feedback to the working > group. Even if your feedback is "this is ready", please let us know. > > Thank you, > > - Mike and Ivaylo > COSE Chairs > > [1]: > https://www.ietf.org/archive/id/draft-ietf-cose-typ-header-parameter-01.html > <https://www.ietf.org/archive/id/draft-ietf-cose-typ-header-parameter-01.html> > > _______________________________________________ > COSE mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/cose _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
