Re: Standardize RSA/SHA256 ?

Jelte Jansen <jelte@NLnetLabs.nl> Fri, 12 May 2006 08:56 UTC

From: Jelte Jansen <jelte@NLnetLabs.nl>
Subject: Re: Standardize RSA/SHA256 ?
Date: Fri, 12 May 2006 10:56:27 +0200
Lines: 45
References: <6.2.5.6.2.20060508094001.03182b80@ogud.com> <Pine.LNX.4.44.0605091629550.31070-100000@citation2.av8.net> <87vesecle7.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enigCA08124CCCBB5B07A498CA45"
X-From: owner-namedroppers@ops.ietf.org Fri May 12 11:06:51 2006
Return-path: <owner-namedroppers@ops.ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.1
User-Agent: Mail/News 1.5 (X11/20060309)
To: namedroppers@ops.ietf.org
In-Reply-To: <87vesecle7.fsf@latte.josefsson.org>
X-Enigmail-Version: 0.94.0.0
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Message-ID:
Message-ID: <20140418072200.2560.7228.ARCHIVE@ietfa.amsl.com>

> 
>> For the above reasons, I think that we have time to consider the
>> correct course of action. There is no need to rush into more
>> algorithms which require more code on nameservers and resolvers.
> 
> Yes, or at least, we need to document a more compelling reason to do
> RSA-SHA-265.
> 

So why is this an issue for RSA/SHA256, and not for
draft-ietf-dnsext-ds-sha256-05.txt, which also makes SHA256 mandatory?

btw, both drafts don't deprecate SHA-1 but do assume that SHA256 is
stronger and contain text about downgrade attacks based on this assumption.

Jelte