Re: [dnsext] Issues in WGLC of dnssec-bis-updates
Mark Andrews <marka@isc.org> Wed, 08 February 2012 10:08 UTC
Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD2D21F84DA; Wed, 8 Feb 2012 02:08:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1328695729; bh=LKiLaGlbgy/VsFZHtIyuyDl3fDZRUeUkXAvtS+4GkO4=; h=To:From:References:In-reply-to:Date:Message-Id:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: MIME-Version:Content-Type:Content-Transfer-Encoding:Sender; b=FRETu8QW5WpFlgRPz3c5BGMzcOKhxt/uFEd/3GKF8MxHFkONY8aRzhq5tL1Nj0Zar KGV9nqpREHyqN7Co4gVqNWHgBbXgQ1I6x8X+Zxpw5mmOs/ZRlU8VHWeTJjLYDCmwZP X2Ir5uJm9Rplp6VrJpmnDo6L0ZuCLdSzdEQB+wwk=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A8821F84E0 for <dnsext@ietfa.amsl.com>; Wed, 8 Feb 2012 02:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level:
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQQ0Pvj-g4iV for <dnsext@ietfa.amsl.com>; Wed, 8 Feb 2012 02:08:47 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id A1B2321F84DA for <dnsext@ietf.org>; Wed, 8 Feb 2012 02:08:47 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 88A61C942D; Wed, 8 Feb 2012 10:08:34 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:fce7:bd7:5736:f19f]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 31895216C6A; Wed, 8 Feb 2012 10:08:34 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id B904D1D02863; Wed, 8 Feb 2012 21:08:34 +1100 (EST)
To: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
From: Mark Andrews <marka@isc.org>
References: <20120207151820.GE9478@crankycanuck.ca> <4F31449C.9040604@nlnetlabs.nl> <a06240801cb570a945202@192.168.128.143> <CACU5sD=bUC9bC_OW4SeH2h6DPM+d3+-JkZyz=6u=dpmj+7rVjw@mail.gmail.com> <4F3232B6.3060505@nlnetlabs.nl>
In-reply-to: Your message of "Wed, 08 Feb 2012 09:30:46 BST." <4F3232B6.3060505@nlnetlabs.nl>
Date: Wed, 08 Feb 2012 21:08:34 +1100
Message-Id: <20120208100834.B904D1D02863@drugs.dv.isc.org>
Cc: dnsext@ietf.org
Subject: Re: [dnsext] Issues in WGLC of dnssec-bis-updates
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org
In message <4F3232B6.3060505@nlnetlabs.nl>, "W.C.A. Wijngaards" writes: > No, the application just wants all bogus data to be removed. Data that > is secure and data that is not DNSSEC signed is what it wants. Because > of the chain-of-trust the validator knows which parts of the space below > a trust anchor is signed (and must have DNSSEC available) and which part > is unsigned. More correctly it knows if it should be able to get a signed answer with signatures it is capable of verifying or not. A zone can be insecure, as far as the validator is concerned, even if there are DS records in the parent zone and the validator treats the parent zone as secure. > This property could be the cause that made insecure and > indeterminate terms exist, as indeterminate is not really processed but > simply the absence of a covering trust anchor, just like in the case > where you had no trust anchors at all. But then insecure needs > processing: you have to validate the chain of trust from the trust > anchor to the insecure-delegation point, and only then can you conclude > that the data is insecure. No, you can conclude that you don't expect to be able to validate it. The break point may or may not be at a insecure delegation (no DS records in parent zone). In reality the first step of validation is determining if there is a trust anchor that is could potentially result in the data being declared secure. From the application's perspective there is no difference if the data came from a zone that was not under a configured trust anchor or from a zone to which there is not a trust chain supported by the validator. > This is something internal to the DNSSEC > validator, and not particularly impressive to the application, that > likely just wants to know if the data was DNSSEC-signed (if so: secure > or bogus) or if the data was not DNSSEC-signed (as determined with the > configured set of trust anchors). No, it want to know if it is secure or insecure (insecure data can still be signed data). Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org _______________________________________________ dnsext mailing list dnsext@ietf.org https://www.ietf.org/mailman/listinfo/dnsext
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates W.C.A. Wijngaards
- [dnsext] Issues in WGLC of dnssec-bis-updates Andrew Sullivan
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates W.C.A. Wijngaards
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Andrew Sullivan
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates W.C.A. Wijngaards
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Edward Lewis
- [dnsext] What is indeterminate Paul Hoffman
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mohan Parthasarathy
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mark Andrews
- Re: [dnsext] What is indeterminate Mark Andrews
- Re: [dnsext] What is indeterminate Paul Hoffman
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates W.C.A. Wijngaards
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mark Andrews
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates bmanning
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Eric Brunner-Williams
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mohan Parthasarathy
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Andrew Sullivan
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Paul Hoffman
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mark Andrews
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mohan Parthasarathy
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Edward Lewis
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mark Andrews
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Mohan Parthasarathy
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates W.C.A. Wijngaards
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Andrew Sullivan
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Samuel Weiler
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Paul Hoffman
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Andrew Sullivan
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Paul Hoffman
- Re: [dnsext] Issues in WGLC of dnssec-bis-updates Wes Hardaker