The most confusing part of COSE, IMO, is the Context Information Structure and Enc_structure. We should address that confusion in this guidance document.
This relates to recent discussion with Orie in the COSE-HPKE document. I’ve written some of what we figured out in SanFran in the t_cose documentation: https://github.com/laurencelundblade/t_cose/blob/dev/inc/t_cose/t_cose_recipient_enc_esdh.h LL On Oct 23, 2023, at 10:23 PM, [email protected] wrote: Les and I think that this draft is also relevant to the COSE group. We have asked for a presentation slot in the JOSE group already but feedback from this group would be appreciated. We have started describing challenges with key identifiers. Ciao Hannes From: jose <[email protected]<mailto:[email protected]>> On Behalf Of [email protected]<mailto:[email protected]> Sent: Dienstag, 24. Oktober 2023 07:20 To: [email protected]<mailto:[email protected]> Subject: [jose] draft-tschofenig-jose-cose-guidance-00 Hi all, Les and I have put together a draft that starts to capture guidance for JOSE (and COSE) following the recent list discussion about key ids (see https://mailarchive.ietf.org/arch/msg/jose/Ziu1dqu9p19U-n1bhR4A5yof5ec/). @Chairs: We would like to have a few minutes at the next IETF JOSE meeting to speak about this document. Here is the link to the draft: https://datatracker.ietf.org/doc/draft-tschofenig-jose-cose-guidance/ Ciao Hannes _______________________________________________ COSE mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/cose
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
