Re: [DNSOP] New Version of draft-ietf-dnsop-algorithm-update-00: Algorithm Implementation Requirements and Usage Guidance for DNSSEC

Ondřej Surý <ondrej@isc.org> Thu, 22 March 2018 17:48 UTC

Return-Path: <ondrej@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62FD8126D45 for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 nqhRlUovYR28 for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 10:48:05 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E3E11200A0 for <dnsop@ietf.org>; Thu, 22 Mar 2018 10:48:05 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 20B153AB069; Thu, 22 Mar 2018 17:48:05 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 0EB93160083; Thu, 22 Mar 2018 17:48:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DB88416006D; Thu, 22 Mar 2018 17:48:04 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id P_r4eMPKHSno; Thu, 22 Mar 2018 17:48:04 +0000 (UTC)
Received: from dhcp-8436.meeting.ietf.org (dhcp-8436.meeting.ietf.org [31.133.132.54]) by zmx1.isc.org (Postfix) with ESMTPSA id 2FA39160047; Thu, 22 Mar 2018 17:48:04 +0000 (UTC)
From: =?utf-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 22 Mar 2018 17:47:58 +0000
References: <EBE54422-0A97-4B33-BD55-01CACF1F272A@isc.org> <alpine.LRH.2.21.1803221314140.11686@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org WG" <dnsop@ietf.org>
In-Reply-To: <alpine.LRH.2.21.1803221314140.11686@bofh.nohats.ca>
Message-Id: <701AEF92-EE3D-4D1C-93ED-F0B5971EC67F@isc.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8RT3xcDDnLiDVUm9dcBSak03E-Q>
Subject: Re: [DNSOP] New Version of draft-ietf-dnsop-algorithm-update-00: Algorithm Implementation Requirements and Usage Guidance for DNSSEC
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 17:48:07 -0000

--
Ondřej Surý
ondrej@isc.org

> On 22 Mar 2018, at 17:27, Paul Wouters <paul@nohats.ca>; wrote:
> 
> On Thu, 22 Mar 2018, Ondřej Surý wrote:
> 
>> https://github.com/oerdnj/draft-ietf-dnsop-algorithm-update
>> 
>> Pull/Merge Requests, Issues, etc. are welcome.
>> 
>> The most of the work done between the last version and this is:
>> 
>> * Removal of MUST-, SHOULD+, etc…
>> * Upgrade the urgency of deploying ECC
>> * Separate operational recommendations for default algorithm to ECDSAP256SHA256
>> * Deprecation of ECC-GOST (that actually happened elsewhere, so we reflect it here)
> 
> As for the DS algorithm 4, SHA-384 does not really add anything over
> SHA-256, so it would be good to move that further down from MAY to MUST
> NOT on the creation (not validation) part. I'm afraid the current
> listing might appear as "it is MAY now but will become MUST in the
> future".
> 
> Based on Viktor's data, the ratio of SHA256 to SHA384 is 500:1 with
> only 8649 DS SHA384 records. Even GOST which is MUST NOT has 4x more
> DS records deployed with 36388 records.

Sounds good to me, you already have access to the repo :).

> I think this text also needs an update:
> 
> 	RSASHA1 and RSASHA1-NSEC3-SHA1 are widely deployed, although zones
> 	deploying it are recommended to switch to ECDSAP256SHA256 as there is
> 	an industry-wide trend to move to elliptic curve cryptography.
> 
> They should switch away from SHA1 as SHA1 is being deprecated industry
> wide. Even if we recommend to move away from RSA (which I'm not sure if there
> is consensus on) to ECC, I would like to move them to ED25519/ED448 over
> the ECDSA* variants.

I don’t think this is currently feasible to do so, so we need to have a feedback from WG.

> If it is too soon for that now, I would simply not
> recommend moving away from RSA. And maybe make ECDSAP256SHA256 a MAY
> instead of a MUST.

What would be the technical/security reason for skipping ECDSA?

Ondrej