Dear all,
Thank you for commenting on this WG LC. The working group last call has concluded. My intention for now is to take care of the shepherd review myself, unless anyone else volunteers (please reach out to me directly if you might be interested in doing this). Thanks again, -- Ivaylo On Thu, Dec 7, 2023 at 6:05β―PM Michael Jones <[email protected]> wrote: > Hi Henk, > > This PR > https://github.com/selfissued/draft-ietf-cose-typ-header-parameter/pull/7/files > updates the spec to uniformly use the term "COSE object", per your > suggestion. It also adds an example of what one is. > > This PR > https://github.com/selfissued/draft-ietf-cose-typ-header-parameter/pull/6/files > adds you to the Acknowledgements. > > We'll merge and publish the draft incorporating all the WGLC comment > resolutions either when we hear back from you or tomorrow. > > Thanks again, > -- Mike > > -----Original Message----- > From: Henk Birkholz <[email protected]> > Sent: Wednesday, November 22, 2023 2:32 PM > To: Ivaylo Petrov <[email protected]>; Cose Chairs Wg <[email protected]>; > cose <[email protected]> > Subject: Re: [COSE] π WGLC of draft-ietf-cose-typ-header-parameter > > +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.i/ > > etf.org%2Farchive%2Fid%2Fdraft-ietf-cose-typ-header-parameter-01.html& > > data=05%7C01%7C%7C55d97957c96a4cf7997b08dbeb91c594%7C84df9e7fe9f640afb > > 435aaaaaaaaaaaa%7C1%7C0%7C638362783560543847%7CUnknown%7CTWFpbGZsb3d8e > > yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C30 > > 00%7C%7C%7C&sdata=JqeHAhq8UBrNfdqOCXnHnA2fz0TnIInWlnkOLdFeKuI%3D&reser > > ved=0 > > <https://www/. > > ietf.org%2Farchive%2Fid%2Fdraft-ietf-cose-typ-header-parameter-01.html > > &data=05%7C01%7C%7C55d97957c96a4cf7997b08dbeb91c594%7C84df9e7fe9f640af > > b435aaaaaaaaaaaa%7C1%7C0%7C638362783560543847%7CUnknown%7CTWFpbGZsb3d8 > > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3 > > 000%7C%7C%7C&sdata=JqeHAhq8UBrNfdqOCXnHnA2fz0TnIInWlnkOLdFeKuI%3D&rese > > rved=0> > > > > _______________________________________________ > > COSE mailing list > > [email protected] > > https://www.i/ > > etf.org%2Fmailman%2Flistinfo%2Fcose&data=05%7C01%7C%7C55d97957c96a4cf7 > > 997b08dbeb91c594%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63836278 > > 3560543847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI > > iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hk0zv2hf6CPhCu5S > > %2BSPmKjxgxko0nPRE1arpNTYl7sA%3D&reserved=0 >
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
