Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC

I would have really liked to be on today's call, but unfortunately will be traveling.

I am really not sure what 'closure' means, but – as expressed by Mountie too – there are many issues tied to SOP based access control and key discoverability. I agree that these are not for current version, but we may want to tag them for a future version rather than close.

Thanks,
Seetharama

On 2/4/13 7:01 AM, "GALINDO Virginie" <Virginie.GALINDO@gemalto.com<mailto:Virginie.GALINDO@gemalto.com>> wrote:

Dear all,

Here is a proposed agenda for our call today @20 UTC
Bridge and irc are the usual ones
+1.617.761.6200, 27978# (CRYPT)
IRC irc.w3.org:6665 #crypto

Regards,
Virginie
Gemalto

---------agenda proposal for 4th of february ------


1- Welcome - 5’

- attendees list

- pick a scribe  - (scribe guide https://www.w3.org/2008/xmlsec/Group/Scribe-Instructions.html  or http://www.w3.org/2008/04/scribe.html )

- agenda approval

- minutes approval from previous meeting http://www.w3.org/2013/01/21-crypto-minutes.html



2- Web Crypto API – 30’

W3C office discussion about IANA registry by Harry Halpin (W3C)

Schedule of JOSE work and dependency with our roadmap by Mike J (Microsoft)

Discussing proposal from editor to close issues
- PROPOSAL: Close ISSUE-40 - How should we define key discovery, noting asynchronicity<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0099.html> Ryan Sleevi
- PROPOSAL: Close ISSUE-37 - Method Naming<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0098.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-34 - Representation of certificates<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0097.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-33 - Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0096.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-32 - API should mention the use of secure elements in the context of key security<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0095.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-31 - Problems with keys attribute of the Crypto interface<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0094.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-30 - How does the application know where the key is stored ?<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0093.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-29 - Handling of block encryption modes and padding<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0091.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0090.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-25 - How do we provision Global Unique ID for pre-provisioned symmetric keys<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0089.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-24 - Defining a Synchronous API<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0088.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0087.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0086.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0085.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0084.html> Ryan Sleevi
-  PROPOSAL: Close ISSUE-10: Making sure our API is usable with pure js environement<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0083.html> Ryan Sleevi

-  PROPOSAL: Close ISSUE-9<http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0082.html>



3- High Level API – 10’

Discussion on the first draft https://dvcs.w3.org/hg/webcrypto-highlevel/raw-file/tip/Overview.html



4- secondary feature discussion – 5’

Define a placeholder for discussing secondary features

4- Group Life – 10’

Our next F2F : proposal of resolution : 24/24 April 2013 in California (in Paypal)



5- AOB – 5’

News from 3GPP http://lists.w3.org/Archives/Public/public-webcrypto/2012Nov/0096.html