Skip to content

[wg/webappsec] Edits for Web Crypto #815

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
simoneonofri wants to merge 2 commits into
base: gh-pages
Choose a base branch
from
Open

[wg/webappsec] Edits for Web Crypto #815

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8bf3b09
[wg/webappsec] Edits for Web Crypto
simoneonofri May 22, 2026
9e25c07
fix
simoneonofri May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions 2026/charter-wg-webappsec-2026.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,10 +218,12 @@ <h2>Scope</h2>
side-channel attacks).</p>
</dd>
<dt><b>WebCrypto</b></dt>
<dd>The WG may adopt well-supported proposals from incubation for maintenance
of the <a href="https://www.w3.org/TR/2017/REC-WebCryptoAPI-20170126/">Web
Cryptography API</a>, such as
<a href="https://wicg.github.io/webcrypto-secure-curves/">secure curves</a>.</dd>
<dd>The WG may adopt well-supported proposals from incubation for the
evolution and maintenance of the
<a href="https://www.w3.org/TR/2017/REC-WebCryptoAPI-20170126/">Web
Cryptography API</a>, including support for additional algorithms,
primitives, or API updates where there is implementer interest,
Web-platform suitability, and Working Group consensus.</dd>
</dl>

<p>In addition to developing Recommendation Track documents in
Expand Down Expand Up @@ -699,6 +701,8 @@ <h3 id="external-coordination">External Organizations</h3><dl>
The IETF is responsible for defining robust and secure protocols for Internet
functionality, in particular HTTP. The Working Group should coordinate
protocol-related work (e.g. cookies) with the appropriate IETF WGs.
For Web Cryptography API work, the Working Group should coordinate
as appropriate with relevant IETF work, including the CFRG.
</dd>
</dl></section>
</section>
Expand Down