Re: [DNSOP] rfc4641bis: NSEC vs NSEC3.

Evan Hunt <each@isc.org> Sat, 20 February 2010 21:29 UTC

Return-Path: <each@isc.org>
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 61A833A8274 for <dnsop@core3.amsl.com>; Sat, 20 Feb 2010 13:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 DLvRN8iJjgso for <dnsop@core3.amsl.com>; Sat, 20 Feb 2010 13:29:43 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 7BABE3A8276 for <dnsop@ietf.org>; Sat, 20 Feb 2010 13:29:43 -0800 (PST)
Received: by farside.isc.org (Postfix, from userid 10292) id 9E424E60B4; Sat, 20 Feb 2010 21:31:33 +0000 (UTC)
Date: Sat, 20 Feb 2010 21:31:33 +0000
From: Evan Hunt <each@isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
Message-ID: <20100220213133.GE2477@isc.org>
References: <200904282021.n3SKL3sg051528@givry.fdupont.fr> <59A58419-FDBD-4810-B2FA-0D293FFA00A5@NLnetLabs.nl> <alpine.LFD.1.10.1001211245180.12114@newtla.xelerance.com> <1AEAE091-2EB3-41DC-A51B-8DD49C10FAD5@NLnetLabs.nl> <24C8A8E2A81760E31D4CDE4A@Ximines.local> <8E6C64ED-A336-4E8B-996F-9FB471EB07C6@NLnetLabs.nl> <4B7FE58C.5030605@ogud.com> <20100220202751.GB54720@shinkuro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100220202751.GB54720@shinkuro.com>
User-Agent: Mutt/1.4.2.3i
Cc: Olaf Kolkman <olaf@NLnetLabs.nl>, dnsop WG <dnsop@ietf.org>, Alex Bligh <alex@alex.org.uk>
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: Sat, 20 Feb 2010 21:29:44 -0000

> I think Olafur's point is a good one, but I'm unhappy with the prose.
> Some suggested changes below.

Same here.

Nits:

> There are to mechanisms to provide authenticated proof of

s/to/two/

> Each mechanism includes a list of all the RRTYPEs present at the

s/includes/stores/

> > The clear text version has its one RRtype for negative answer, Clear  
> > text one uses NSEC record and the obfuscated one used NSEC3.
> 
> I didn't know how to rephrase that, because if I understand it I think
> what I understand is wrong (but that's obviously not the case, so
> probably I don't understand it).

I think he meant "each version has its own RRtype".  Suggested change:

"Each mechanism uses a specific RRTYPE to store information about the
RRTYPEs present at the name: the clear-text mechanism uses NSEC, and
the obfuscated-data mechanism uses NSEC3."

It may also be worth mentioning that the two mechanisms are usually
referred to by the names of their corresponding RR types.

--
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.