IETF Logo Mail Archive

Re: [Dcrup] rsa-sha1 usage

"John Levine" <johnl@taugh.com> Wed, 14 June 2017 16:45 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 8C6AB129C00 for <dcrup@ietfa.amsl.com>; Wed, 14 Jun 2017 09:45:47 -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 aD4F4ApwSMXa for <dcrup@ietfa.amsl.com>; Wed, 14 Jun 2017 09:45:46 -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 B9615128B4E for <dcrup@ietf.org>; Wed, 14 Jun 2017 09:45:45 -0700 (PDT)
Received: (qmail 96876 invoked from network); 14 Jun 2017 16:45:44 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Jun 2017 16:45:44 -0000
Date: Wed, 14 Jun 2017 13:51:23 -0000
Message-ID: <20170614135123.4861.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dcrup@ietf.org
Cc: phill@hallambaker.com
In-Reply-To: <CAMm+LwjiHiD0JGscz4d-3w3joPkzoVzxZVXzLwvW8EH-kFjxnw@mail.gmail.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/rRplfvtWtXHcBhuyHHY7WSOmMbQ>
Subject: Re: [Dcrup] rsa-sha1 usage
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: Wed, 14 Jun 2017 16:45:48 -0000

In article <CAMm+LwjiHiD0JGscz4d-3w3joPkzoVzxZVXzLwvW8EH-kFjxnw@mail.gmail.com> you write:
>DKIM is an IETF specification. If IETF makes a change then M3AAWG will
>almost certainly follow suit. But I do not think it at all likely
>M3AAWG would start making suggestions on technical matters like this
>in preference to IETF action.

Hi from the M3AAWG meeting in Lisbon.

M3 publishes the occasional BCP, not standards. There's been a fair
amount of hall conversations about how to get the signers still using
sha-1 to switch.

R's,
John

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