Re: [Dcrup] I-D draft-ietf-dcrup-dkim-crypto-06

Scott Kitterman <sklist@kitterman.com> Mon, 18 September 2017 17:31 UTC

Return-Path: <sklist@kitterman.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 693C2133070 for <dcrup@ietfa.amsl.com>; Mon, 18 Sep 2017 10:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=kitterman.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 JhXIJCsjOLry for <dcrup@ietfa.amsl.com>; Mon, 18 Sep 2017 10:31:41 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27792132992 for <dcrup@ietf.org>; Mon, 18 Sep 2017 10:31:41 -0700 (PDT)
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 5CA69C401C9 for <dcrup@ietf.org>; Mon, 18 Sep 2017 12:31:39 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2001409; t=1505755899; bh=gVNEBxokQACW0XIJntQiXuh7+ru0t82Maw0xcjX8cz8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HcsIBI5J/pkCZQXgLUzeAN+rWzM31IRPbUYWJxb0T5UoUTOrK4iat67pAZjble/O+ HdSOnNYJE2P3ArTKK6uPR8hTTSpAh6Dwt2RZPMWqD7ukmn/I18E4yheC6cFi1gSGmf KryWesAEbThOwMHnYaipTgvF/F+5vt0X7Xf2MhZk=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Mon, 18 Sep 2017 13:31:38 -0400
Message-ID: <1853334.xPrzCzLMPD@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-125-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <a771978b-5e1c-2885-914a-ff465f41e9eb@bluepopcorn.net>
References: <20170916051535.2177.qmail@ary.lan> <a771978b-5e1c-2885-914a-ff465f41e9eb@bluepopcorn.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/vBKxQLs6hy2rdkMhGXtsAmxlIIk>
Subject: Re: [Dcrup] I-D draft-ietf-dcrup-dkim-crypto-06
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: Mon, 18 Sep 2017 17:31:42 -0000

On Monday, September 18, 2017 10:13:52 AM Jim Fenton wrote:
> On 9/15/17 10:15 PM, John Levine wrote:
> > In article <1739837.QWERb01LVO@kitterma-e6430> you write:
> >>> As far as I can tell, this is about as done as it's going to get.
> >> 
> >> Do we really need to add both rsafp and ed25519?
> >> 
> >> I thought we had ~agreed (or at least discussed) earlier to only add
> >> ed25519> 
> > In July I proposed only doing EC but there was no consensus.  I would
> > prefer not to rerun old arguments unless we have learned something new in
> > the meantime.
> I haven't found your proposal, but I asked on Jabber at the Prague
> meeting whether one or the other would suffice, and repeated that
> question on the list. See thread "Do we need both hashed RSA and
> elliptic curves?" that begins on 21 July. There were responses from 7
> people including you, and I didn't see anyone arguing that we should
> have both (although it's not my place to judge consensus).
> 
> We would be doing a disservice if we require everyone to support two
> ways of solving the key length problem unless there is a compelling
> reason to do so.
> 
> I also support the use of elliptic curve signatures rather than rsafp.
> Part of the reason is that rsafp may have IPR issues (see disclosure
> 3025). AFAIK EC signatures avoid this problem unless the selector DNS
> record contains a hash of the public key, which shouldn't be necessary
> because the key is shorter. I have no opinion on the choice of curve used.

Those all make sense to me.

I don't recall anyone pushing hard for retaining both and, while I agree there 
was never a formal consensus call by the chairs, it seemed like that was 
definitely the direction the group was leaning.

Scott K