Re: [DNSOP] New Version Notification for draft-muks-dnsop-dnssec-sha3-00.txt

"Paul Hoffman" <paul.hoffman@vpnc.org> Wed, 05 April 2017 14:24 UTC

Return-Path: <paul.hoffman@vpnc.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 68CC4127BA3 for <dnsop@ietfa.amsl.com>; Wed, 5 Apr 2017 07:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 8SycRmc7tUQy for <dnsop@ietfa.amsl.com>; Wed, 5 Apr 2017 07:24:11 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 0E14A126DC2 for <dnsop@ietf.org>; Wed, 5 Apr 2017 07:24:11 -0700 (PDT)
Received: from [10.32.60.144] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v35ENtDh096722 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Apr 2017 07:23:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [10.32.60.144]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Mukund Sivaraman <muks@isc.org>
Cc: dnsop@ietf.org
Date: Wed, 05 Apr 2017 07:24:11 -0700
Message-ID: <39B58207-4CC2-420B-B774-2766FC80B194@vpnc.org>
In-Reply-To: <20170405084256.GA22692@jurassic>
References: <20170405084256.GA22692@jurassic>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AoaWAPmUGgha5MNO2ea64Uhw2tg>
Subject: Re: [DNSOP] New Version Notification for draft-muks-dnsop-dnssec-sha3-00.txt
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: Wed, 05 Apr 2017 14:24:12 -0000

On 5 Apr 2017, at 1:42, Mukund Sivaraman wrote:

>> Name:		draft-muks-dnsop-dnssec-sha3

NIST's use case for SHA3 algorithms is for when particular SHA2 
algorithms are weakened. This would mean that the fallback for RSASHA256 
is RSASHA512, not a SHA3 variant. Thus, the premise for this entire 
draft (which isn't listed until the end...) is flawed.

Also, it is weird that a draft that is about having a fallback if a hash 
algorithm becomes weakened uses the RSASSA-PKCS1-v1_5 signature scheme, 
given that PKCS1 1.5 is already known to be weakened.

--Paul Hoffman