I'm not saying we need to add any curves in particular, just that we shouldn't lock ourselves out of binary curves altogether. If we ever want to add a binary curve, the current format is insufficient.
On Fri, Aug 16, 2013 at 1:40 PM, Russ Housley <[email protected]> wrote: > Richard: > > I still think there's value in basing this in SEC1, since it gives us > binary curves. > > > I do not know if you are advocating every aspect of SEC1 or not. > > Experience to date has shown that support for arbitrary curves does not > get implemented. For this reason, we have been focusing on well-known > curves such as the NIST curves and the Brainpool curves. An identifier is > sufficient to provide all of the curve parameters. The SEC1 format > supports this using an object identifier. That seems like the wrong form > for a jose identifier. > > Russ > > >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
