Re: [Dcrup] I-D Action: draft-ietf-dcrup-dkim-crypto-03.txt

"John R Levine" <johnl@taugh.com> Sun, 02 July 2017 19:53 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C7D127137 for <dcrup@ietfa.amsl.com>; Sun, 2 Jul 2017 12:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=3GoMMSfU; dkim=pass (1536-bit key) header.d=taugh.com header.b=bLJGfsLB
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 WMx0U-wrVrHF for <dcrup@ietfa.amsl.com>; Sun, 2 Jul 2017 12:53:20 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22B5A1201F8 for <dcrup@ietf.org>; Sun, 2 Jul 2017 12:53:19 -0700 (PDT)
Received: (qmail 90628 invoked from network); 2 Jul 2017 19:53:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=16202.59594f2e.k1707; bh=RZ5f4vZdBpIBcxeurB/y0mFlDRtkYNw9TMSYuszVgHE=; b=3GoMMSfUxwhXgRCwHgHqrjLVDjfeL40QvJYVS16uDMhOXHdG1MaRIRnhUXUhBhsTXzvovXkxzGvPE2Z2uQXtOsQgFxkL2zCnwpqBjz4Et2R/JC20hxbvTiveJwL9fKl2LfI/bVVyJIbhUcNA9kqsPad9uCnNUUW+f92Kk+ioK7mHDg3cTTDzIELQsWH3MC/f3jTkFQBPbKngBv74KPUrlnZOka0WfJW/fhqScamJD0fmycUPZuo7V/ZplLh6BLgr
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=16202.59594f2e.k1707; bh=RZ5f4vZdBpIBcxeurB/y0mFlDRtkYNw9TMSYuszVgHE=; b=bLJGfsLBlJw3ZIi84MfHJ4SOUwiWu8rh0upQ0aHxHl4tk015q5IagODXQ3DtblZ8Yut1/7O1Pj/WoGqlPGkF9CTottmJlUu7t6oD2l+37W6BnSUp+7m8ypI/d4DO92KNayRzthftMquyOWx7HrZgRAE6weOxTc7reJ6C6xyCeC77Is1a3Nm8jBoFJ6L9ZM917vlqFyJExKHiRLeYZhHNfibNhdh2D+9blKEF18cqBJy+NF8C2mSPhWe78l0r0P95
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 02 Jul 2017 19:53:18 -0000
Date: Sun, 02 Jul 2017 15:53:18 -0400
Message-ID: <alpine.OSX.2.21.1707021544590.72907@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: dcrup@ietf.org
In-Reply-To: <CABcZeBOLSrYo8mEQ1evyU7CzctV0VF4r7_bX3nA0oxtHCeEgSQ@mail.gmail.com>
References: <CABcZeBOs1yZ7q3oBgNeVkw=zSQb_SuS4hqK8BH0ebrD5LRYTFg@mail.gmail.com> <20170702025650.55902.qmail@ary.lan> <CABcZeBM4KEr5CEZq4t9BX50btCRPLhZBAtZN18v_6gZ5B-ni5A@mail.gmail.com> <alpine.OSX.2.21.1707012341180.70305@ary.qy> <CABcZeBOLSrYo8mEQ1evyU7CzctV0VF4r7_bX3nA0oxtHCeEgSQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/dyATiVSPS-xAx1ZGsq00ZxDq8uY>
Subject: Re: [Dcrup] I-D Action: draft-ietf-dcrup-dkim-crypto-03.txt
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2017 19:53:22 -0000

> Given that (a) we already have algorithms that are bigger and (b) 
> post-quantum keys might be quite a bit bigger, it seems unwise to design 
> under the assumption that it will not happen.

Well, OK, but concretely, what do you want us to do now?

DKIM has had algorithm tags since it was defined a decade ago.  This draft 
adds two new algorithm tags (rsafp-sha256 and eddsa-sha256) and deprecates 
one old one (rsa-sha1) and as part of that adds RSA key hashes as a key 
verification method.  If it turns out that we need to switch signature 
algorithms, we'll revise DKIM again, and add and deprecate tags and 
algorithms as needed.  Maybe new algorithms will use key hashes, maybe 
they won't, but at that point we can define whatever we need.

Right now, today, I don't see that hasned ed25519 keys solve any problem, 
so I'm not going to include them unless there is something I don't 
understand that they can do that plain ed25519 keys in the key records 
don't.

R's,
John