RE: Selective Disclosure for W3C Data Integrity

It is good to see this gap filled and I appreciate that there will now exist implementation approaches both for the near term and with a road map for the future, whichever credential proof formats one chooses to use to protect your credential.

Secured Using Data Integrity Proofs >> SD-DI (Selective Disclosure w/ FIPS Compliant Cryptography) >> BBS for DI (Selective Disclosure + Unlinkability)

Secured Using VC-JWT >> SD-JWT (Selective Disclosure w/ FIPS Compliant Cryptography) >> JWP (Selective Disclosure + Unlinkability)

Looking forward to learning more of the details.

Best Regards,

Anil

Anil John
Technical Director, Silicon Valley Innovation Program 
Science and Technology Directorate 
US Department of Homeland Security 
Washington, DC, USA 

Email Response Time – 24 Hours


-----Original Message-----
From: Manu Sporny <msporny@digitalbazaar.com> 
Sent: Monday, May 29, 2023 2:52 AM
To: W3C Credentials CG <public-credentials@w3.org>
Subject: Selective Disclosure for W3C Data Integrity

CAUTION: This email originated from outside of DHS. DO NOT click links or open attachments unless you recognize and/or trust the sender. Contact your component SOC with questions or concerns.


Hi CCG'ers (VCWG bcc'd),

Today, we are announcing a selective disclosure capability for W3C Data Integrity that is compatible with NIST-compliant cryptography. As many of you know, the Data Integrity specification and a few cryptosuites are being standardized in the W3C Verifiable Credentials WG.

There has been a gap for a while now that made it not possible to meet selective disclosure use cases using NIST compliant cryptography. This is an important requirement that needs to be met for national government and large enterprise use cases. This announcement now makes it possible to meet those use cases.

A slide deck outlining this new capability is attached to this email and provided in the link below:

https://urldefense.us/v3/__https://docs.google.com/presentation/d/1d-04kIWhPuNscsAyUuRH3pduqrNerhigCWahKe6SNos/edit*__;Iw!!BClRuOV5cvtbuNI!G6mJsx09CsS3dF6ce4wlkxC1QzihFLyfYYLFP0SgAGhojIWDijQk4UoKc6MCxNrwzV7soYZeSG6X-040d1dprbx10A$


There is a complete implementation of the mechanism available here, that works with the Verifiable Credentials v2.0 work as well as the ECDSA cryptosuite that is already adopted by the Working Group:

https://urldefense.us/v3/__https://github.com/digitalbazaar/ecdsa-sd-2023-cryptosuite__;!!BClRuOV5cvtbuNI!G6mJsx09CsS3dF6ce4wlkxC1QzihFLyfYYLFP0SgAGhojIWDijQk4UoKc6MCxNrwzV7soYZeSG6X-040d1c-f-ojnw$


We look forward to feedback on the approach and interoperable implementations as the work progresses in the public. We are also happy to answer any questions or concerns that you might have regarding the work.

-- manu

--
Manu Sporny - https://urldefense.us/v3/__https://www.linkedin.com/in/manusporny/__;!!BClRuOV5cvtbuNI!G6mJsx09CsS3dF6ce4wlkxC1QzihFLyfYYLFP0SgAGhojIWDijQk4UoKc6MCxNrwzV7soYZeSG6X-040d1dOLRAoMw$

Founder/CEO - Digital Bazaar, Inc.
https://urldefense.us/v3/__https://www.digitalbazaar.com/__;!!BClRuOV5cvtbuNI!G6mJsx09CsS3dF6ce4wlkxC1QzihFLyfYYLFP0SgAGhojIWDijQk4UoKc6MCxNrwzV7soYZeSG6X-040d1dzWAA7tg$

Received on Tuesday, 30 May 2023 12:07:50 UTC