FYI -- posted to p...@ietf.org. Intended to work together with draft-josefsson-tls-eddsa or draft-josefsson-tls-eddsa2.
/Simon From: Simon Josefsson <si...@josefsson.org> Subject: Updated elliptic curve drafts To: p...@ietf.org Date: Mon, 12 Oct 2015 22:25:31 +0200 Hi, I've updated my drafts on Curve25519/Curve448 support in PKIX to refer to the CFRG-Curves and CFRG-EdDSA drafts. The following document adds new EdDSA key/signature OIDs directly: https://tools.ietf.org/html/draft-josefsson-pkix-eddsa-04 The following document adds new namedCurve OIDs, thus going indirectly through the existing ECDSA 3279 route: https://tools.ietf.org/html/draft-josefsson-pkix-newcurves-01 These two drafts take different approaches to including the new curves into PKIX, and currently both lack applicability statements. There is potential for overlap and conflict right now. It recently came up that for PKCS#11 a namedCurve approach would be useful, but for normal PKIX Certificates, it may be that the first direct approach is preferrable. The former lack the possibility of encoding keys for DH. I believe each approach can be useful on its own, but we need to include text adressing use-cases that can be resolved by both documents to avoid conflicts. /Simon
signature.asc
Description: PGP signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
