ISSUE-40: How should we define key discovery, noting asynchronicity

How should we define key discovery, noting asynchronicity

State:
CLOSED
Product:
Web Crypto Key Discovery API
Raised by:
Opened on:
2012-09-17
Description:
As decided during our call on the 4th of March, the issue is closed.
http://www.w3.org/2013/03/04-crypto-minutes.html
Related Actions Items:
No related actions
Related emails:
  1. [minutes] Re: W3C Web Crypto WG - monday 4th of march (from wseltzer@w3.org on 2013-03-04)
  2. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
  3. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
  4. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
  5. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
  6. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
  7. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
  8. RE: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from Virginie.GALINDO@gemalto.com on 2013-03-04)
  9. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
  10. W3C Web Crypto WG - take away of our 18th of Feb conf call (from Virginie.GALINDO@gemalto.com on 2013-02-25)
  11. W3C Web Crypto WG - classifying issues (from Virginie.GALINDO@gemalto.com on 2013-02-18)
  12. Re: W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC (from hhalpin@w3.org on 2013-02-18)
  13. W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-02-17)
  14. PROPOSAL: CLOSE ISSUE-40: How should we define key discovery, noting asynchronicity (from Virginie.GALINDO@gemalto.com on 2013-02-11)
  15. Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from watsonm@netflix.com on 2013-02-11)
  16. Re: W3C Web Crypto WG - classifying issues (from sleevi@google.com on 2013-02-07)
  17. Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from sleevi@google.com on 2013-02-07)
  18. Re: PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  19. PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  20. PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  21. PROPOSAL: Postpone ISSUE-26: Should key generation be allowed to specify multi-origin access (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  22. PROPOSAL: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  23. PROPOSAL: Postpone ISSUE-34: Representation of Certificates (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
  24. PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from sleevi@google.com on 2013-02-07)
  25. W3C Web Crypto WG - classifying issues (from Virginie.GALINDO@gemalto.com on 2013-02-07)
  26. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from watsonm@netflix.com on 2013-02-04)
  27. RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Asad.Ali@gemalto.com on 2013-02-04)
  28. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from S.Durbha@cablelabs.com on 2013-02-04)
  29. W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-02-04)
  30. PROPOSAL: Close ISSUE-40 - How should we define key discovery, noting asynchronicity (from sleevi@google.com on 2013-01-31)
  31. W3C Web Crypto WG - Take Away from 17th of september call (from Virginie.GALINDO@gemalto.com on 2012-09-18)
  32. [minutes] Re: W3C Web Crypto WG - agenda for 17th of september call - today (from wseltzer@w3.org on 2012-09-17)
  33. ISSUE-40: How should we define key discovery, noting asynchronicity (from sysbot+tracker@w3.org on 2012-09-17)

Related notes:

[hhalpin]: Key import/export

18 Feb 2013, 20:14:43

as mentionned in the Take away from 18th of feb 2013, the issue is closed, as having been adressed by the reation of the web crypto WG.

Virginie GALINDO, 25 Feb 2013, 16:29:46

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 40.html,v 1.1 2017/02/13 16:16:52 ted Exp $