[security-request] Issue: Verifiable Credential Data Integrity (and vc-di-eddsa and vc-di-ecdsa) 2023-05-27 -> 2023-07-31 (#55) marked as REVIEW REQUESTED

msporny has just labeled an issue for https://github.com/w3c/security-request as "REVIEW REQUESTED":

== Verifiable Credential Data Integrity (and vc-di-eddsa and vc-di-ecdsa) 2023-05-27 -> 2023-07-31 ==
- Name of specs to be reviewed:
  * [Verifiable Credential Data Integrity](https://www.w3.org/TR/vc-data-integrity/)
  * [EdDSA Cryptosuite v2022](https://www.w3.org/TR/vc-di-eddsa/)
  * [ECDSA Cryptosuite v2019](https://www.w3.org/TR/vc-di-ecdsa/)

- URL of specs:
  * [Verifiable Credential Data Integrity](https://www.w3.org/TR/vc-data-integrity/)
  * [EdDSA Cryptosuite v2022](https://www.w3.org/TR/vc-di-eddsa/)
  * [ECDSA Cryptosuite v2019](https://www.w3.org/TR/vc-di-ecdsa/)

- What and when is your next expected transition?
  - Transition to Candidate Recommendation in September 2023 (at W3C TPAC)
- What has changed since any previous review?
  - There has bee no previous review of these specifications
- Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html)
  - https://github.com/w3c/vc-data-integrity/issues/98
- Where and how to file issues arising?
  - https://github.com/w3c/vc-data-integrity/issues
- Pointer to any explainer for the spec?
  - https://www.w3.org/TR/vc-data-integrity/#introduction

Other comments:

The three specifications listed above are cryptographic message securing mechanisms and are intended to be reviewed together. The first specification, Verifiable Credential Data Integrity, is the base specification that defines the base concepts and algorithms. The "EdDSA Cryptosuite" and "ECDSA Cryptosuite" specifications are concrete implementations of the base specification and each define specific cryptographic algorithms and processes to be used when providing data integrity protection for Verifiable Credentials.

See https://github.com/w3c/security-request/issues/55


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 27 May 2023 19:38:41 UTC