ISSUE-17: Define the scope and API for custom key attributes

Define the scope and API for custom key attributes

State:
CLOSED
Product:
key definition for Web Crypto API
Raised by:
Ryan Sleevi
Opened on:
2012-08-06
Description:
During the July Face-to-Face, vgb proposed a definition of key attributes grouped into three categories - functional, advisory/supplementary, and scope.

Of these, only functional attributes (such as the algorithm family, size, usage) were seen as immutable attributes. Advisory/supplementary and scope represent potentially mutable attributes for an application. Some may be provided, but not enforced, by the user agent, whereas others may be wholly defined and enforced by the underlying application.

For attributes defined by the application, the question is whether to define a custom storage mechanism on the Key object, or whether they should be implemented by applications via existing web platform APIs. An example of an existing API might be utilizing localStorage ( http://www.w3.org/TR/webstorage/ ) or IndexedDB ( http://www.w3.org/TR/IndexedDB/ ) to associate attributes with the key, using the Key's ID as a key with the underlying storage mechanism.

Arguments In Favor:
- It tightly couples supplementary attributes with Keys, allowing pre-provisioned Keys to have pre-provisioned attributes exposed via the API.
- Clearing the IndexedDB or Web Storage will not erase application-critical attributes for keys.

Arguments Against:
- It represents yet-another-Key-Value-storage mechanism, except this one tightly coupled to Keys
Related Actions Items:
No related actions
Related emails:
  1. W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-04-12)
  2. [W3C Web Crypto WG] PROPOSAL: Close ISSUE-17 (Define the scope and API for custom key attributes) (from Virginie.GALINDO@gemalto.com on 2013-04-04)
  3. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from rbarnes@bbn.com on 2013-03-04)
  4. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from watsonm@netflix.com on 2013-03-04)
  5. 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)
  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 Virginie.GALINDO@gemalto.com on 2013-03-04)
  8. 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)
  9. 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)
  10. Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from rbarnes@bbn.com on 2013-02-08)
  11. Algorithm attribute (was Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes ) (from sleevi@google.com on 2013-02-06)
  12. Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from sleevi@google.com on 2013-02-06)
  13. Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from rbarnes@bbn.com on 2013-02-05)
  14. Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from sleevi@google.com on 2013-02-04)
  15. Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from rbarnes@bbn.com on 2013-02-04)
  16. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from watsonm@netflix.com on 2013-02-04)
  17. RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Asad.Ali@gemalto.com on 2013-02-04)
  18. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from S.Durbha@cablelabs.com on 2013-02-04)
  19. W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-02-04)
  20. PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (from sleevi@google.com on 2013-01-31)
  21. Re: ISSUE-17: Key Attributes - Proposed resolution (from mzollinger@netflix.com on 2012-09-05)
  22. Re: ISSUE-17: Key Attributes - Proposed resolution (from sleevi@google.com on 2012-09-05)
  23. Re: ISSUE-17: Key Attributes - Proposed resolution (from mzollinger@netflix.com on 2012-09-05)
  24. Re: ISSUE-17: Key Attributes - Proposed resolution (from sleevi@google.com on 2012-09-04)
  25. Re: ISSUE-17: Key Attributes - Proposed resolution (from mzollinger@netflix.com on 2012-09-04)
  26. Re: ISSUE-17: Key Attributes - Proposed resolution (from arun@mozilla.com on 2012-09-04)
  27. RE: ISSUE-17: Key Attributes - Proposed resolution (from Vijay.Bharadwaj@microsoft.com on 2012-09-04)
  28. RE: ISSUE-17: Key Attributes - Proposed resolution (from Vijay.Bharadwaj@microsoft.com on 2012-09-04)
  29. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from mountie.lee@mw2.or.kr on 2012-09-01)
  30. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-31)
  31. Re: ISSUE-17: Key Attributes - Proposed resolution (from sleevi@google.com on 2012-08-31)
  32. Re: ISSUE-17: Key Attributes - Proposed resolution (from mzollinger@netflix.com on 2012-08-30)
  33. RE: ISSUE-17: Key Attributes - Proposed resolution (from Vijay.Bharadwaj@microsoft.com on 2012-08-28)
  34. ISSUE-17: Key Attributes - Proposed resolution (from sleevi@google.com on 2012-08-27)
  35. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-27)
  36. RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-27)
  37. [W3C Web Crypto WG] functional features list in draft API and issue tracker (from Virginie.GALINDO@gemalto.com on 2012-08-22)
  38. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from watsonm@netflix.com on 2012-08-22)
  39. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from sleevi@google.com on 2012-08-21)
  40. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from watsonm@netflix.com on 2012-08-21)
  41. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from sleevi@google.com on 2012-08-21)
  42. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from watsonm@netflix.com on 2012-08-21)
  43. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from sleevi@google.com on 2012-08-21)
  44. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from watsonm@netflix.com on 2012-08-21)
  45. Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (from sleevi@google.com on 2012-08-21)
  46. Re: [W3C Web Crypto WG] functional features list in draft API and issue tracker (from sleevi@google.com on 2012-08-21)
  47. [W3C Web Crypto WG] functional features list in draft API and issue tracker (from Virginie.GALINDO@gemalto.com on 2012-08-21)
  48. Re: Support for generic authentication tokens (from mzollinger@netflix.com on 2012-08-21)
  49. Re: Support for generic authentication tokens (from sleevi@google.com on 2012-08-17)
  50. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-17)
  51. Re: Support for generic authentication tokens (from mzollinger@netflix.com on 2012-08-14)
  52. RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-14)
  53. Re: Support for generic authentication tokens (from sleevi@google.com on 2012-08-10)
  54. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from ddahl@mozilla.com on 2012-08-08)
  55. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-08)
  56. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-08)
  57. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from ddahl@mozilla.com on 2012-08-08)
  58. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from hhalpin@w3.org on 2012-08-08)
  59. crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-06)
  60. New Editor's Draft (from sleevi@google.com on 2012-08-05)
  61. Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (from sleevi@google.com on 2012-08-05)

Related notes:

Closed per http://www.w3.org/2013/04/15-crypto-minutes.html

hhalpin: RESOLVED: http://www.w3.org/2012/webcrypto/track/issues/17is closed and the answer is there will not be an API for custom key attributes

Ryan Sleevi, 15 Apr 2013, 20:19:55

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: 17.html,v 1.1 2017/02/13 16:16:50 ted Exp $