[openpgp] Ed25519 in a draft

Daniel Huigens <d.huigens@protonmail.com> Wed, 28 April 2021 15:54 UTC

Return-Path: <d.huigens@protonmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D0D7C3A11E5 for <openpgp@ietfa.amsl.com>; Wed, 28 Apr 2021 08:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Status: No, score=-2.819 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id E1guDvnRCza2 for <openpgp@ietfa.amsl.com>; Wed, 28 Apr 2021 08:54:41 -0700 (PDT)
Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch []) (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 0EE043A11EB for <openpgp@ietf.org>; Wed, 28 Apr 2021 08:54:40 -0700 (PDT)
Date: Wed, 28 Apr 2021 15:54:22 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1619625278; bh=opZKob3M+OwvHuL8gSWbHGnp985/bFW9y6h2VvDz0KA=; h=Date:To:From:Reply-To:Subject:From; b=ua/AbRhDIckl3g9Ph7XoNZA/mzfiRFWats5tfVHs9TiPytH8YPKP+5KQxrtAa5CQT xx3I7SmFfOuAcGOoVyMiRbWRKBsM/cGtWlnAkOw+JCF1Xisxi+fCGv+QSrPMIt0ans +a1f9Okdt1br0TUV+bLijlYFP3dw+wrQXCOqwcUQ=
To: "openpgp@ietf.org" <openpgp@ietf.org>
From: Daniel Huigens <d.huigens@protonmail.com>
Reply-To: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <sU3FUMNkHv6tddQD5InZ98sqTN4H6PCCl8EhXgxp4hO8zw_o-wXWgDYshjoii8y7ufljLjE4vw8hF_GCqD5vH-DJAtqPgQWU6-N0x7S2M-k=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/KAn-KvO0rBYAW5oqs1zVr8yZjcg>
Subject: [openpgp] Ed25519 in a draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2021 15:54:52 -0000

Hi all, and dear editors,

Would it be possible to get a new draft out with Ed25519 in it?

(I'm not sure if this work is blocked by anything, but I'm sending
this email purely in case some encouragement is helpful ^.^
Let me know if I can do anything more helpful than that.)

We (OpenPGP.js) would like to switch to generating ECC keys by
default, and the current situation where Ed25519 is not in any
non-expired draft is a bit awkward, in that context.

(FWIW, I also care about a bunch of other stuff in rfc4880bis,
but this one seems the most uncontroversial to me ^.^)

Thanks for all your work!

Daniel Huigens