Re: Web Cryptography Working Group scoping progressing...

Dear all. I want to comment something.

in scope

1) How about adding API access to control of SSL/TLS login?

2) I think some of API interfaces for personal certificate management are
needed such as import and export of keypair although most of browsers have
own certificate manager.

3) Some of functions as like key pare generation and digital signature
generation require browser's user interface. It needs universal interface
guideline for security issues. Please add "guideline of universal user
interface in browser" and . For examples,
http://html5.creation.net/webcrypto-api/#login-with-the-user-certificate.
This is related to indentity APIs like BrowerID. Also it may be included in
recommendation-track deliverables similar with http://www.w3.org/TR/wsc-ui/

out of scope

a compatiblity between keystore in each browsers. Some applications can try
a same keypare management in them.

Channy
---------------------
Mozilla Korea Community, http://www.mozilla.or.kr
Technology Evangelist, Daum Developers Network & Affiliates
http://dna.daum.net


2011/11/3 Harry Halpin <hhalpin@w3.org>

> Everyone,
>
> While the use-cases need to be more compelling and I'm pretty sure the
> browser-specific language is still present, the scoping is getting closer
> we think:
>
> http://www.w3.org/wiki/IdentityCharter
>
> This was created after the meeting at TPAC on the "break-out" session.
>
>   cheers,
>         harry
>
>
>