Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds

"John Levine" <johnl@taugh.com> Sat, 10 June 2017 03:04 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 E246C128854 for <dcrup@ietfa.amsl.com>; Fri, 9 Jun 2017 20:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1DKXFCTJHApF for <dcrup@ietfa.amsl.com>; Fri, 9 Jun 2017 20:04:24 -0700 (PDT)
Received: from miucha.iecc.com (w6.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 3BD6C12009C for <dcrup@ietf.org>; Fri, 9 Jun 2017 20:04:24 -0700 (PDT)
Received: (qmail 91391 invoked from network); 10 Jun 2017 03:04:22 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 Jun 2017 03:04:22 -0000
Date: Sat, 10 Jun 2017 03:04:00 -0000
Message-ID: <20170610030400.12835.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dcrup@ietf.org
Cc: sklist@kitterman.com
In-Reply-To: <CBFF8363-08F6-419E-AB24-D26137627C76@kitterman.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/7ttd3aKeHjRDg9yMm7CXeO4Js8c>
Subject: Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds
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: Sat, 10 Jun 2017 03:04:26 -0000

In article <CBFF8363-08F6-419E-AB24-D26137627C76@kitterman.com> you write:
>>Given that we are nowhere close to deciding what elliptic algorithm(s)
>>to add, it seems kind of premature to me.
>
>Why would that matter?  This draft just gets rid of the obsolete cruft.  It clears the deck for adding a new
>algorithm, but in no way requires we have that sorted out.

I had the perhaps overoptimistic hope that we could wrap up the new
algorithm reasonably quickly and update DKIM once rather than twice.

There is a significant cost to each RFC, both in what it costs to
produce it, and to people's attention in the future.  The more places
you spread around the spec, the more likely it is that people will
miss part of it.

If it's going to take us another year to decide which elliptic curve
to use and whether to add key hashes, then OK, we can push this out
now, but I hope we can do better than that.

R's,
John