ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG

Relationship between the W3C Web Cryptography work product and the IETF JOSE WG

State:
CLOSED
Product:
Web Cryptography API
Raised by:
Ryan Sleevi
Opened on:
2012-08-06
Description:
During IETF 84, a frequent question asked was about the relationship between the W3C Web Cryptography API work product and the IETF JOSE WG work product.

As currently spec'd in 1.10, an AlgorithmIdentifier is an (Algorithm or DOMString). This was added in response to ACTION-7, which was to permit string identifiers as names for algorithms.

Two issues arise from this:
1) Is the additional complexity for handling EITHER an Algorithm OR a DOMString worthwhile to the API? The result of ACTION-7 was the introduction of the Algorithm Normalizing Rules, which adds additional complexity for mapping between DOMStrings to Algorithms.
2) Should the specification directly refer to the JOSE Algorithms (JWA)?
Related Actions Items:
No related actions
Related emails:
  1. Re: IANA registry for WebCrypto? (from sleevi@google.com on 2013-01-23)
  2. Re: IANA registry for WebCrypto? (from rbarnes@bbn.com on 2013-01-23)
  3. Re: IANA registry for WebCrypto? (from sleevi@google.com on 2013-01-18)
  4. Re: IANA registry for WebCrypto? (from rbarnes@bbn.com on 2013-01-18)
  5. RE: IANA registry for WebCrypto? (from Michael.Jones@microsoft.com on 2013-01-18)
  6. Re: IANA registry for WebCrypto? (from rbarnes@bbn.com on 2013-01-18)
  7. Re: IANA registry for WebCrypto? (from sleevi@google.com on 2013-01-18)
  8. Re: IANA registry for WebCrypto? (from rbarnes@bbn.com on 2013-01-18)
  9. Re: IANA registry for WebCrypto? (from sleevi@google.com on 2013-01-18)
  10. RE: New Editor's Draft Published (from karen.lu@gemalto.com on 2012-09-04)
  11. New Editor's Draft Published (from sleevi@google.com on 2012-08-31)
  12. Re: Proposed text to close ISSUE-13 (from wtc@google.com on 2012-08-29)
  13. RE: Proposed text to close ISSUE-13 (from Asad.Ali@gemalto.com on 2012-08-29)
  14. RE: Proposed text to close ISSUE-13 (from Michael.Jones@microsoft.com on 2012-08-29)
  15. Proposed text to close ISSUE-13 (from sleevi@google.com on 2012-08-29)
  16. RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-27)
  17. Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (from sleevi@google.com on 2012-08-22)
  18. Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (from watsonm@netflix.com on 2012-08-22)
  19. crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-22)
  20. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from wtc@google.com on 2012-08-21)
  21. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from sleevi@google.com on 2012-08-17)
  22. RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from Michael.Jones@microsoft.com on 2012-08-17)
  23. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from sleevi@google.com on 2012-08-17)
  24. RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from Michael.Jones@microsoft.com on 2012-08-17)
  25. RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-14)
  26. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from hhalpin@w3.org on 2012-08-10)
  27. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from jarred@webkit.org on 2012-08-08)
  28. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from sleevi@google.com on 2012-08-08)
  29. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from ddahl@mozilla.com on 2012-08-08)
  30. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from wtc@google.com on 2012-08-08)
  31. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from hhalpin@w3.org on 2012-08-08)
  32. crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-06)
  33. New Editor's Draft (from sleevi@google.com on 2012-08-05)
  34. Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (from sleevi@google.com on 2012-08-05)

Related notes:

Related mails are also
http://lists.w3.org/Archives/Public/public-webcrypto/2012Aug/0069.html and http://lists.w3.org/Archives/Public/public-webcrypto/2012Aug/0068.html mentioning possible evolution of JOSE spec.

Virginie GALINDO, 13 Aug 2012, 13:56:45

During the 6th of August conf call, the consensus was that the JOSE work would be reused as much as possible, but that the Web Crypto API would be more expressive in order to address the low level targeted. This has to be sorted out by the editors.

Virginie GALINDO, 13 Aug 2012, 21:21:55

Tentative resolution in r1.31. JOSE has been explicitly added to use cases, with possible additions to Scope of document in the future.

JOSE work should be enabled and supported by this API, but it does not necessarily mean that JOSE support is mandated by this API.

Ryan Sleevi, 30 Aug 2012, 23:01:32

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