Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-updates-16
Mark Andrews <marka@isc.org> Sat, 28 January 2012 13:43 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 BC23621F8577; Sat, 28 Jan 2012 05:43:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1327758236; bh=nLJld7hKLjAT6wwwiJpfIf6atMbaggGqeGKVKUs4pN0=; 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=eLGzXpe6d0O3EG8OiAKMXNZqZYRoEhPkC68hU+Ejo605LBGHSp9e8L8O2fMWZ0u6U Zx11GDdZLBttstWyOsONEudxNEMf3JQhcXFnCMI7tBQONMnAqL6G/cnGHtFJiernOJ fmTDRRq/uVzuUCZEfev14OE7kJgL8s5RL5V5Ig2I=
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 79FBA21F8576 for <dnsext@ietfa.amsl.com>; Sat, 28 Jan 2012 05:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level:
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 v2hCJftNGYXl for <dnsext@ietfa.amsl.com>; Sat, 28 Jan 2012 05:43:52 -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 2237321F853B for <dnsext@ietf.org>; Sat, 28 Jan 2012 05:43:49 -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 0200FC9478; Sat, 28 Jan 2012 13:43:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:69a2:4c28:157f:527e]) (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 67BED216C6B; Sat, 28 Jan 2012 13:43:35 +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 819221C33944; Sun, 29 Jan 2012 00:43:31 +1100 (EST)
To: Mohan Parthasarathy <suruti94@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20120120054939.GD4365@mail.yitter.info> <CACU5sDnS-3V26yKyvTGObR67H2LPiBjWxCZAbMpHPZrgXJeNFg@mail.gmail.com> <20120128052029.618CE1C32BFA@drugs.dv.isc.org> <CACU5sD=P-agE2oOqvAiCs=bcX3Off6cCubW-f=skKP54-1oQaQ@mail.gmail.com>
In-reply-to: Your message of "Fri, 27 Jan 2012 22:11:43 -0800." <CACU5sD=P-agE2oOqvAiCs=bcX3Off6cCubW-f=skKP54-1oQaQ@mail.gmail.com>
Date: Sun, 29 Jan 2012 00:43:31 +1100
Message-Id: <20120128134331.819221C33944@drugs.dv.isc.org>
Cc: DNSEXT Working Group <dnsext@ietf.org>
Subject: Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-updates-16
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 <CACU5sD=P-agE2oOqvAiCs=bcX3Off6cCubW-f=skKP54-1oQaQ@mail.gmail.com> , Mohan Parthasarathy writes: > On Fri, Jan 27, 2012 at 9:20 PM, Mark Andrews <marka@isc.org> wrote: > > > > In message <CACU5sDnS-3V26yKyvTGObR67H2LPiBjWxCZAbMpHPZrgXJeNFg@mail.gmai= > l.com> > > , Mohan Parthasarathy writes: > > > >> - Section 5.7 setting the AD bit on queries. Is CD=0,DO=0 in the que= > ry > >> same as AD=1,DO=0 ? > > > > The question doesn't make sense. > > > > AD=0,DO=1 and AD=1,DO=1 produce the same result. > > AD=0,DO=0 and AD=1,DO=0 produce different results. > > AD=0,DO=0 and AD=0,DO=1 produce different results. > > AD=1,DO=0 and AD=0,DO=1 produce different results. > > > Thanks for the clarification. I realized after I posted that not > setting CD and DO is pre-DNSSEC. > > >> missed the discussion on this earlier. If there is a valid reason, > >> that needs to be stated explicitly as to why we are introducing this > >> new option. > > > > Section 5.7 explains why this option exists. > > > > This allows a requestor to indicate that i= > t understands > > the AD bit without also requesting DNSSEC data via the DO bit. > > > > > So, "understands" here means "Please do the validation for me " ? > Then, is CD=1, AD=1 a invalid option ? No. AD will be 1 if the answer + authority sections come from cached data that has validated as secure. That said I don't think there is much use unless you are trying to check if a lookup failure was due to DNSSEC errors. > So, there are implementations out there that want to know whether > validation was successful or not but just not want to handle any > DNSSEC records? I will put it this way. I doubt if there is a application that cares about AD that *wants* the DNSSEC records. At the moment they have no choice unless they are using the draft. > My question was more on what prompted the addition of this new feature ? 1. It reduces the response size. 2. You can apply DNS64, NXDOMAIN redirection, bad site filtering, etc. with AD=1 which you can't with DO=1. 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
- [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-updat… Andrew Sullivan
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Andrew Sullivan
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Edward Lewis
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… W.C.A. Wijngaards
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mohan Parthasarathy
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mohan Parthasarathy
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mohan Parthasarathy
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Warren Kumari
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Michael StJohns
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Matthijs Mekking
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Paul Hoffman
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Blacka, David
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mohan Parthasarathy
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Samuel Weiler
- Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-bis-u… Mark Andrews