Re: [Curdle] Which curves are MUST and SHOULD ?

Simo Sorce <simo@redhat.com> Tue, 01 December 2020 18:58 UTC

Return-Path: <simo@redhat.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE3C3A1448 for <curdle@ietfa.amsl.com>; Tue, 1 Dec 2020 10:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpahgji7FlPv for <curdle@ietfa.amsl.com>; Tue, 1 Dec 2020 10:58:32 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A08AC3A1342 for <curdle@ietf.org>; Tue, 1 Dec 2020 10:58:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606849111; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rbBBHvHj2a8zWvtiWc7NL9VuYm4gi+TXW5Pi78sjQp0=; b=MzrlsS/RNCWW8KayyUb0BkMOKohsHpk2DMdXGz0v3zMLICmiVPPlTIi/n0u3bGyCYOWwHz X963VwOz0N3JDKiGqXKz6odkVFs4hBiYdyMO/eabk1JHoS04FwzwKnTMD+Jbo6fs1UtiGF d0V2BWn1PkbzCFGzZeTMOKaXD3RvrmQ=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-549-M7Z-2ktfM6yVIANiB6mOSw-1; Tue, 01 Dec 2020 13:57:24 -0500
X-MC-Unique: M7Z-2ktfM6yVIANiB6mOSw-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 57137858182; Tue, 1 Dec 2020 18:57:23 +0000 (UTC)
Received: from ovpn-115-14.phx2.redhat.com (ovpn-115-14.phx2.redhat.com [10.3.115.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0920360BD8; Tue, 1 Dec 2020 18:57:21 +0000 (UTC)
Message-ID: <4b681efd49274f03c7e0521e127e031426632ad0.camel@redhat.com>
From: Simo Sorce <simo@redhat.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "Mark D. Baushke" <mdb=40juniper.net@dmarc.ietf.org>, "curdle@ietf.org" <curdle@ietf.org>
Date: Tue, 01 Dec 2020 13:57:20 -0500
In-Reply-To: <2CCABC30-F757-4659-9FF3-5AADDD51EE30@akamai.com>
References: <2CCABC30-F757-4659-9FF3-5AADDD51EE30@akamai.com>
Organization: Red Hat, Inc.
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=simo@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/bmmPuJU7MFQ8v20FlkSiGR6GUbQ>
Subject: Re: [Curdle] Which curves are MUST and SHOULD ?
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 18:58:34 -0000

On Tue, 2020-12-01 at 16:38 +0000, Salz, Rich wrote:
> >    PS: Note I have NOT uploaded the -13 edition of the document pending
>     feedback/consensus on the ecdh-sha2-nistp{256,384,512} being SHOULD
>     instead of MUST. I would be more likely to want curve25519-sha256 to be
>     a MUST rather than SHOULD than the nistp curves be a MUST... mostly due
>     to personal bias.
> 
> Pulling this topic into a separate thread.
> 
> If you have opinions on NIST and X25519, please speak up now.

I do not personally have any bias toward NIST vs x25519 curves, but in
practice the x25519 curve should be a MUST because it is the most
widely deployed, while the NIST curves should be a SHOULD because of
wide adoption in FIPS environments.

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc