IETF Logo Mail Archive

Re: [DNSOP] draft-fujiwara-dnsop-nsec-aggressiveuse-01.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sat, 24 October 2015 19:18 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521291A6F90 for <dnsop@ietfa.amsl.com>; Sat, 24 Oct 2015 12:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-Omhw3H0UAK for <dnsop@ietfa.amsl.com>; Sat, 24 Oct 2015 12:18:09 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C75C61A6F7F for <dnsop@ietf.org>; Sat, 24 Oct 2015 12:18:08 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 871A93BBCA; Sat, 24 Oct 2015 21:18:06 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id CEA2B190B21; Sat, 24 Oct 2015 21:16:54 +0200 (CEST)
Date: Sat, 24 Oct 2015 21:16:54 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: 神明達哉 <jinmei@wide.ad.jp>
Message-ID: <20151024191654.GA3560@sources.org>
References: <20150310.191541.52184726.fujiwara@jprs.co.jp> <20150707.182043.193693838.fujiwara@jprs.co.jp> <CAJE_bqcRQH0WGTaLqtMSuiOty4KHe9nN6T-wmqf3x_ohuA6TcA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJE_bqcRQH0WGTaLqtMSuiOty4KHe9nN6T-wmqf3x_ohuA6TcA@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.2
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/-KAF6IBa2r1hDUWGYdtc3kDJQ6E>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-fujiwara-dnsop-nsec-aggressiveuse-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 24 Oct 2015 19:18:10 -0000

[Re-reading all emails...]

On Fri, Jul 10, 2015 at 11:53:30AM -0700,
 神明達哉 <jinmei@wide.ad.jp> wrote 
 a message of 62 lines which said:

> Regarding Section 5 (possible side effect on root servers), I wonder
> about the implication of qname-minimization (which I expect will be
> deployed much sooner than this proposal).  A resolver that supports
> qname-minimization would first send a query to "local." to the root
> server upon receiving a "foo.local" query, and cache the result of
> NXDOMAIN for "local.".  It will suppress subsequent external queries
> for any subdomain of it.

Yes. Qname minimization relies on the fact that resolvers follow the
tree structure of the DNS. If "toto." does not exist, it means
"foobar.toto." certainly does not exist and there is no point querying
any authoritative server about it, a resolver can send back NXDOMAIN
immediately.

In ietf-dnsop-qname-minimisation-07, it is discussed in section 3.

v2.23.0 | Report a Bug | By Email