CfC to move WebCrypto-2 to CR < 2025-07-16

[simoneonofri]

This is a Call for Consensus (CfC) to move Web Cryptography API Level 2 as a Candidate Recommendation (CR).

This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.

We discussed this briefly in our most recent WG meeting, with no objections raised.

To ensure everyone has an opportunity to weigh in, this issue will serve as a record of the group's decision, one way or another.

I've pre-populated this issue with reactions to make it trivial to collect a signal from folks out there in the world:

• React with👍 if you agree with the publication.
• React with 😕 if you disagree, but it's fine if we decide to proceed.
• React with 👎 if you strongly disagree with the publication.

If you register discontent with the publication, please add a comment as well so we know what we can address to remove the concern (and if you really disapprove, Formal Objections are accepted through the usual venues).

You can find the most recent editor's draft at https://w3c.github.io/webcrypto/.

Thanks!

Please respond by 2025-07-16, at which point I'll close this CfC and open an issue to coordinate the preparation.

[cc'ing @twiss ]

[simoneonofri]

Having received no objections, I proceed

[simoneonofri]

Follow-up on #690