IETF Logo Mail Archive

Re: [Dcrup] I-D Action: draft-ietf-dcrup-dkim-usage-00.txt

Russ Housley <housley@vigilsec.com> Fri, 02 June 2017 18:54 UTC

Return-Path: <housley@vigilsec.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 12549126E01 for <dcrup@ietfa.amsl.com>; Fri, 2 Jun 2017 11:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 QvpqoPDc81Cl for <dcrup@ietfa.amsl.com>; Fri, 2 Jun 2017 11:54:53 -0700 (PDT)
Received: from mail.smeinc.net (x-bolt-wan.smeinc.net [209.135.219.146]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 899851200E5 for <dcrup@ietf.org>; Fri, 2 Jun 2017 11:54:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id EC6F33005A4 for <dcrup@ietf.org>; Fri, 2 Jun 2017 14:54:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id d_iiTG0g2zu8 for <dcrup@ietf.org>; Fri, 2 Jun 2017 14:54:51 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 6F20A3004AF; Fri, 2 Jun 2017 14:54:51 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <EDB418F9-32E9-40C9-8466-3D3A1B113200@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A77FB047-F152-43B1-BFEC-EB4DD06B6355"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 02 Jun 2017 14:54:51 -0400
In-Reply-To: <CAL0qLwZ1oqmghnMqyQnr6t6ZD3q-Gjj3gROhobsWkJWVkbxq+g@mail.gmail.com>
Cc: dcrup@ietf.org
To: "Murray S. Kucherawy" <superuser@gmail.com>, Kurt Andersen <kurta@drkurt.com>
References: <149619233095.19793.14947085917778354002@ietfa.amsl.com> <3745683.4zdJlR4cAU@kitterma-e6430> <CABuGu1o7Bp4MA1mgTBHhTrTR3Kcb=u3AMxZfqcuO=TNOThhdyw@mail.gmail.com> <CAL0qLwZ1oqmghnMqyQnr6t6ZD3q-Gjj3gROhobsWkJWVkbxq+g@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/8HY8o31gn-eQovF3GU0q8WiJmlw>
Subject: Re: [Dcrup] I-D Action: draft-ietf-dcrup-dkim-usage-00.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: Fri, 02 Jun 2017 18:54:55 -0000

> On Jun 2, 2017, at 1:35 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> (sans chapeau)
> 
> I realize I have some threads to catch up on, but...
> 
> On Thu, Jun 1, 2017 at 9:49 PM, Kurt Andersen <kurta@drkurt.com <mailto:kurta@drkurt.com>> wrote:
> I think that this does not quite go far enough in shifting the algorithms and acceptable key lengths into an IANA registry to future-proof the spec and allow more rapid response in the case of exploit advancement.
> 
> I'd like to see both of those pieces "out sourced" to a registry with updates to be driven by crypto-competent people.
> 
> This notion feels weird to me.  What would such a registry look like?  Are there any other protocol registries that contain just a list of key sizes or lengths of things currently approved by the community?  What would the update rules be on such a registry?

I am aware of some registries that include a column to mark aged algorithms as “Not recommended.”

I have not seen a registry that included a minimum key size column.

Russ

v2.28.0 | Report a Bug | By Email | System Status