Hi Mike I can understand the desire to create alignment with RFC 7638 since the symmetric key thumbprint functionality is also supported there. It might nevertheless be good to state the use case in the draft and I couldn't follow Brendan's explanation during the meeting. He had some use case for TEEP or SUIT in mind.
Ciao Hannes Von: Michael Jones <[email protected]> Gesendet: Donnerstag, 27. Juli 2023 17:10 An: Tschofenig, Hannes (T CST SEA-DE) <[email protected]>; [email protected]; [email protected] Cc: cose <[email protected]> Betreff: RE: draft-ietf-cose-key-thumbprint-00.txt [chair hat off] I would suggest supporting symmetric key thumbprints, so as to be parallel with JWK Thumbprint, which does so at https://www.rfc-editor.org/rfc/rfc7638.html#section-3.2. -- Mike From: COSE <[email protected]<mailto:[email protected]>> On Behalf Of Tschofenig, Hannes Sent: Thursday, July 27, 2023 4:54 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: cose <[email protected]<mailto:[email protected]>> Subject: [COSE] draft-ietf-cose-key-thumbprint-00.txt We have submitted the -00 version of the COSE Key Thumbprint draft. At the meeting John and Brendan raised two additional requirements, namely * Support for thumbprints of symmetric keys, * Support for thumbprints of CWT Claims Sets and CBOR Web Tokens Due to lack of time at the COSE session it was not possible to go into the details about those two requirements. @John+@Brendan: Could you give us more context? Ciao Hannes
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
