Re: Rewriting SD-JWT in Deterministically Encoded CBOR

On 2023-12-06 18:29, Orie Steele wrote:
> There is: https://datatracker.ietf.org/doc/draft-prorock-cose-sd-cwt/ <https://datatracker.ietf.org/doc/draft-prorock-cose-sd-cwt/>
> 
> We have an implementation here: https://github.com/transmute-industries/sd-cwt <https://github.com/transmute-industries/sd-cwt>
> 
> SD-CWT was one of the proposed protocol documents for the SPICE BoF.
> 
> See https://datatracker.ietf.org/group/spice/about/ <https://datatracker.ietf.org/group/spice/about/>
> 
> Draft charter: https://github.com/transmute-industries/ietf-spice-charter <https://github.com/transmute-industries/ietf-spice-charter>
> 
> Meetings are in the readme ^ if you are interested in joining.

Thanx!  I was not aware of this work.

My take on this is NOT based on the COSE "container" since Deterministically Encoded CBOR eliminates hiding everything in bstr.  The resulting structures are (as shown by the example), considerably neater and trivial to implement.

Trying out the "COSE challenger": https://test.webpki.org/csf-lab/home.

Anders

> 
> OS
> 
> On Wed, Dec 6, 2023 at 11:16 AM Anders Rundgren <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote:
> 
>     Spurred by the adoption of Deterministically Encoded CBOR as an IETF work item, I intend (as an experiment...), recast SD-JWT in this souped up take on CBOR.
> 
>     The following document should give you an idea of what to expect: https://github.com/cyberphone/D-CBOR#example <https://github.com/cyberphone/D-CBOR#example>
> 
>     Anders
> 
> 
> 
> -- 
> 
> 
> ORIE STEELE
> Chief Technology Officer
> www.transmute.industries
> 
> <https://transmute.industries>
> 

Received on Wednesday, 6 December 2023 17:40:17 UTC