Re: [openpgp] Summary of WG status

"brian m. carlson" <sandals@crustytoothpaste.net> Thu, 10 August 2017 01:48 UTC

Return-Path: <sandals@crustytoothpaste.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED78129B25 for <openpgp@ietfa.amsl.com>; Wed, 9 Aug 2017 18:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (3072-bit key) header.d=crustytoothpaste.net
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 dcddbergLero for <openpgp@ietfa.amsl.com>; Wed, 9 Aug 2017 18:48:02 -0700 (PDT)
Received: from castro.crustytoothpaste.net (castro.crustytoothpaste.net [75.10.60.170]) (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 C5A7F13251A for <openpgp@ietf.org>; Wed, 9 Aug 2017 18:48:02 -0700 (PDT)
Received: from genre.crustytoothpaste.net (unknown [IPv6:2001:470:b978:101:254c:7dd1:74c7:cde0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by castro.crustytoothpaste.net (Postfix) with ESMTPSA id 6A39E280AD for <openpgp@ietf.org>; Thu, 10 Aug 2017 01:47:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=crustytoothpaste.net; s=default; t=1502329678; bh=jKqEyf4PpS/4857W0l/ZdY/B9H79eaWHkoxew4ybiG4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=jzPXdj4KZv0BvJcGcqaQKma0uEVxg2u6fNqUL6PxnbDgv+KqenLOWs3T5O+wrSumA 6dyjnAVIu9Zq5cuInp3/uEllLMKbzAP86A0Unky2bZer46U+uJqtk9s3vy6Y1a1cH+ YikiHBG1q8cqsZwIH4FVMGYjm21/YJ2ZH6I4+YW/fNv2V/EVVND/Ti/cgvmMFSRSBM L9vhfw1Xl3DZiVhifo0gdHjvPaSVxWXLTsoLnwfp+HPk5TuhKSjGKadO3eL2OKuCQH b31vnf72G3fIYhS0DUlVuUWcoIfKa+xP1kW5NjCTIwZyn3cO/qOSX3H5C/nOg+dPJe 2b9Qh9myXok2avZkON5dUhOCtt1pkf8I2gkVeY1bE3U+vZL/Y8IRSx8GyZ4i+/LADe fddvCwhV/CpJtLNIT23ygAkHrNschStRqC61Czos7aHg86669nwy37uXs7Bdzt/3Br 5ConX5knKS75YTirYYHrOQ4xaztdeHCd0Ch16ZWK8mFn1XdaQu9
Date: Thu, 10 Aug 2017 01:47:51 +0000
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: openpgp@ietf.org
Message-ID: <20170810014751.erufvruh2lm5cdpe@genre.crustytoothpaste.net>
References: <20170712223852.zmnvw4iwvziqsynq@genre.crustytoothpaste.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dr3ru5txr4yqitd5"
Content-Disposition: inline
In-Reply-To: <20170712223852.zmnvw4iwvziqsynq@genre.crustytoothpaste.net>
X-Machine: Running on genre using GNU/Linux on x86_64 (Linux kernel 4.11.0-2-amd64)
User-Agent: NeoMutt/20170609 (1.8.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/ZSsJcxyYNt5i5p216pdTG0AolKs>
Subject: Re: [openpgp] Summary of WG status
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 10 Aug 2017 01:48:06 -0000

On Wed, Jul 12, 2017 at 10:38:52PM +0000, brian m. carlson wrote:
> Our charter includes several goals that we should accomplish.  I'm going
> to summarize where we are with each of them so we can see where we need
> to make progress.
> 
> If you're going to respond to one or more of these, please respond to
> each one in a separate thread so that we can have a logical set of
> discussions.
> 
> CFRG Curves
> -----------
> 
> We've included EdDSA with Curve25519.  I'd suggest including Curve448 as
> an additional option for EdDSA.  That might necessitate including
> SHAKE256 limited to this purpose only.
> 
> Curve25519 is defined for ECDH.  We probably also want to consider
> Curve448.  The work needed for this purpose is probably limited to
> including OIDs for the curve.

While I'm thinking about it, did anyone have any opinions on adding
Curve448 support?  If we decide not to add it now, we could always do an
update in a future RFC if we change our minds later.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204