[pkix] Updated elliptic curve drafts

Simon Josefsson <simon@josefsson.org> Mon, 12 October 2015 20:25 UTC

Return-Path: <simon@josefsson.org>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 62D321B3608 for <pkix@ietfa.amsl.com>; Mon, 12 Oct 2015 13:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0DUs-S1Orshe for <pkix@ietfa.amsl.com>; Mon, 12 Oct 2015 13:25:41 -0700 (PDT)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BD921B3606 for <pkix@ietf.org>; Mon, 12 Oct 2015 13:25:41 -0700 (PDT)
Received: from latte.josefsson.org ([]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id t9CKPWrP001363 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <pkix@ietf.org>; Mon, 12 Oct 2015 22:25:33 +0200
X-Hashcash: 1:22:151012:pkix@ietf.org::e8gN9EWFgOOYncoC:5kQk
From: Simon Josefsson <simon@josefsson.org>
To: pkix@ietf.org
OpenPGP: id=54265E8C; url=http://josefsson.org/54265e8c.txt
Date: Mon, 12 Oct 2015 22:25:31 +0200
Message-ID: <87fv1fal6s.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
X-Virus-Scanned: clamav-milter 0.98.7 at duva.sjd.se
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/TPFZN9HAP6eDA6PyCRBN_hK5YtU>
Subject: [pkix] Updated elliptic curve drafts
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 20:25:44 -0000


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:


The following document adds new namedCurve OIDs, thus going indirectly
through the existing ECDSA 3279 route:


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.