Tess: This is a request to add a specific set of algorithms to the WebCrypto API... we asked them to fill out the missing bits of our issue template, and their answer left a lot of fields N/A or unknown.

... We got a response 4 days ago, from the person who filed the request, explaining that they are from the 360 browser. They mentioned the QQ browser also support the proposal.

... In the past the Web Cryptography WG have been reluctant to add this type of algorithm. If that WG still existed, they would be the right people to make this call, but they don't.

David: There has been some discussion about chartering a new Web Crypto WG; still uncertain about whether that will go ahead.

Tess: Is there something we can cite about best practices? It would be nice to be able to point to some kind of industry consensus.

(brief discussion of whether there's any IETF stuff written down)

David: In general, the consensus seems to be that we want fewer cryptography algorithm options, with a high bar for inclusion.

Tess: Let's come back to this in two weeks.

... discussion of web crypto...

When the web crypto group closed, they said to send future reqeuests to the public-web-security mailing list. We are hence going to close this issue and refer the requestor to that mailing list.

Tess: This doesn't seem to have a viable venue, given that the Web Crypto WG doesn't exist any more. These specs aren't being maintained, so it's unclear how this change would make it into the spec. Would be nice to get a sense from them that they see a way forward.

David: The WebCrypto group was disbanded because they finished their spec. Probably around 2017.

Tess: [standard complaint re: disbanding groups which define APIs that need to be maintained]

... Already raised the issue about venue in April. Not sure what to do with this.

... We're not the right people to help with process/governance issues, per our charter.

Tess: Let's take this one to plenary.