secp256k1 with COSE is now registered in the IANA COSE registries [1]. The RFC you're looking for would be under RFC8812 [2]. [1]: https://www.iana.org/assignments/cose/cose.xhtml [2]: https://www.rfc-editor.org/rfc/rfc8812.html ________________________________ From: Christopher Allen <ChristopherA@lifewithalacrity.com> Sent: Monday, February 14, 2022 11:22 AM To: Leonard Rosenthol <lrosenth@adobe.com> Cc: Julien Fraichot <Julien.Fraichot@hyland.com>; Manu Sporny <msporny@digitalbazaar.com>; Mike Prorock <mprorock@mesur.io>; Nikos Fotiou <fotiou@aueb.gr>; Orie Steele <orie@transmute.industries>; W3C Credentials CG <public-credentials@w3.org> Subject: Re: [EXTERNAL] [jfraichot@learningmachine.com] Re: VC API: handling large documents client to server 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. On Sun, Feb 13, 2022 at 8:07 AM Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>> wrote: So why not move to CBOR and COSE instead of JWT? Leonard, Any news on using secp256k1 with COSE? We are increasingly using CBOR for all of our cryptocurrency related wallet interoperability standards, but everything I’ve seen for COSE with secp has expired. FYI, our CBOR list is at https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-006-urtypes.md, those that are unique to our work start at 300. — Christopher Allen [via iPhone]
Received on Sunday, 13 February 2022 23:24:56 UTC