IETF Logo Mail Archive

Re: [DNSOP] rfc4641bis: NSEC vs NSEC3.

Andrew Sullivan <ajs@shinkuro.com> Mon, 22 February 2010 18:50 UTC

Return-Path: <ajs@shinkuro.com>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F315A3A7FB0 for <dnsop@core3.amsl.com>; Mon, 22 Feb 2010 10:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.986
X-Spam-Level:
X-Spam-Status: No, score=-1.986 tagged_above=-999 required=5 tests=[AWL=0.613, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3536g8YYhPH5 for <dnsop@core3.amsl.com>; Mon, 22 Feb 2010 10:50:00 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 51E823A7D67 for <dnsop@ietf.org>; Mon, 22 Feb 2010 10:50:00 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4A8A81ECB4E8 for <dnsop@ietf.org>; Mon, 22 Feb 2010 18:51:59 +0000 (UTC)
Date: Mon, 22 Feb 2010 13:51:57 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsop@ietf.org
Message-ID: <20100222185157.GO64954@shinkuro.com>
References: <24C8A8E2A81760E31D4CDE4A@Ximines.local> <8E6C64ED-A336-4E8B-996F-9FB471EB07C6@NLnetLabs.nl> <4B7FE58C.5030605@ogud.com> <20100220202751.GB54720@shinkuro.com> <20100220213133.GE2477@isc.org> <4B807DC0.9050807@ogud.com> <315AD36E-879A-4512-A6A8-B64372E3D3CF@sinodun.com> <201002220022.o1M0M3qR048760@drugs.dv.isc.org> <d3aa5d01002212013x50993902xa8be099c09aefd16@mail.gmail.com> <20100222161758.GF2228@dul1mcmlarson-l1-2.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100222161758.GF2228@dul1mcmlarson-l1-2.local>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [DNSOP] rfc4641bis: NSEC vs NSEC3.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 22 Feb 2010 18:50:01 -0000

On Mon, Feb 22, 2010 at 11:17:59AM -0500, Matt Larson wrote:

>   I am adamantly opposed to including
> any text about SHA1 hash collisions in an NSEC3 context.

Add me to the choir.  Actually, I'm opposed to including any text
about SHA-1 hash collisions in _any_ DNSSEC context until we write the
document, "Deprecating SHA-1 hash functions for DNSSEC".  

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

v2.23.0 | Report a Bug | By Email