The decisions about what algorithms to include and what implementation requirements to place on them has largely been data driven. The working group produced a survey of what algorithms are implemented on what development platforms (attached) and used it to drive these decisions. For the most part, those algorithms that are commonly implemented by the libraries are required, and those that are not, are not. The goal was the broadest practical interoperability possible.
-- Mike
-----Original Message-----
From: Daniel Holth [mailto:[email protected]]
Sent: Thursday, November 21, 2013 11:12 AM
To: Richard Barnes
Cc: Mike Jones; Dirkjan Ochtman; jose
Subject: Re: [jose] JWS algorithms: DSA, non-NIST curves
> Honestly, I don't really care format what the software takes. It's
> pretty trivial to convert between the compressed format and (x,y).
I'm not sure which way you're arguing here.
I also like to just use the 32-byte public key instead of or as the kid (just
transmitting the public key with each signature).
> On the other hand, I could see defining something different for the
> private key, since it's not directly a point multiplier.
Would be cool to see Ed25519 in this spec. It has been a useful specification
so far. That is all.
Platform_Support_for_JWA-04_Crypto_Algorithms.xlsx
Description: Platform_Support_for_JWA-04_Crypto_Algorithms.xlsx
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
