Re: [dnsext] Clarifying the mandatory algorithm rules

Paul Vixie <vixie@isc.org> Mon, 22 November 2010 17:32 UTC

Return-Path: <vixie@vix.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F9E23A6A3E for <dnsext@core3.amsl.com>; Mon, 22 Nov 2010 09:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 JKP7iyCpwELz for <dnsext@core3.amsl.com>; Mon, 22 Nov 2010 09:32:36 -0800 (PST)
Received: from nsa.vix.com (unknown [IPv6:2001:4f8:3:bb:230:48ff:fe5a:2f38]) by core3.amsl.com (Postfix) with ESMTP id 2E5B43A6A3A for <dnsext@ietf.org>; Mon, 22 Nov 2010 09:32:36 -0800 (PST)
Received: from nsa.vix.com (localhost [127.0.0.1]) by nsa.vix.com (Postfix) with ESMTP id 0266FA1037 for <dnsext@ietf.org>; Mon, 22 Nov 2010 17:33:30 +0000 (UTC)
From: Paul Vixie <vixie@isc.org>
To: dnsext@ietf.org
In-Reply-To: Your message of "Mon, 22 Nov 2010 07:58:53 EST." <a06240801c9101620d463@[192.168.128.163]>
References: <alpine.BSF.2.00.1011180553250.83352@fledge.watson.org> <4CE51293.5040605@nlnetlabs.nl> <a06240801c9101620d463@[192.168.128.163]>
X-Mailer: MH-E 8.2; nmh 1.2; XEmacs 21.4 (patch 22)
Date: Mon, 22 Nov 2010 17:33:29 +0000
Message-ID: <22284.1290447209@nsa.vix.com>
Sender: vixie@vix.com
Subject: Re: [dnsext] Clarifying the mandatory algorithm rules
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 17:32:37 -0000

> Date: Mon, 22 Nov 2010 07:58:53 -0500
> From: Edward Lewis <Ed.Lewis@neustar.biz>
> ...
> DNSSEC is designed to protect against cache poisoning.  If there is a chain
> of trust to an RRSet, then the set validates, it has proven source
> authenticity and data integrity.
> 
> Since time began (for DNS), there is always something wrong somewhere.  The
> goal is a robust system, not a tightly correct system.

+1.