IETF Logo Mail Archive

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

Shumon Huque <shuque@gmail.com> Tue, 14 July 2015 17:13 UTC

Return-Path: <shuque@gmail.com>
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 9CAB21A8A65 for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2015 10:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 Di4nmeKhwOp9 for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2015 10:13:26 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9951D1A8A54 for <dnsop@ietf.org>; Tue, 14 Jul 2015 10:13:24 -0700 (PDT)
Received: by qgep37 with SMTP id p37so7140204qge.1 for <dnsop@ietf.org>; Tue, 14 Jul 2015 10:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=nfxpUuyL3WRxyD6uTMLWkTbJgRuuXsTYOuq5O3jOCO4=; b=i9A0YhgCoqQulKKLtRVU/OMyjXqk0vP9BtXolZhENTWv5g574rmGOGT/uRPAK07PQM YwNk1EotPuJJknwhECT0NETbzoH+tcXbpESe3d5kf6OREtLWeja/Gg8GQjjy76VKBppJ 19S1HVqZAjVau0fVdmwlRpNIVOH6WJ6d/Hmqpkm3/nBALKEyjYQewyiKm9Azt0bMAdoq 6wPpZO0oYoE0csufjr4ZU1NMGWb+7GgpfJP8fsfV+KLo2+F554DCA3HHObZnLgM6rjGi nCyCwnHsQtQIrHlFna/y4kcBJWnP7RiRQ13WyhXAJ4oYAdc64oGHkoFVfuZ+vTo2mp5p 2hFA==
MIME-Version: 1.0
X-Received: by 10.140.85.85 with SMTP id m79mr64083786qgd.37.1436894003921; Tue, 14 Jul 2015 10:13:23 -0700 (PDT)
Received: by 10.140.80.208 with HTTP; Tue, 14 Jul 2015 10:13:23 -0700 (PDT)
In-Reply-To: <CAJE_bqdAuOns+1tjsXpyEsoaYHtcHH+=HSThMcjhUEkCX0gGxw@mail.gmail.com>
References: <20150310.191541.52184726.fujiwara@jprs.co.jp> <20150707.182043.193693838.fujiwara@jprs.co.jp> <CAJE_bqcRQH0WGTaLqtMSuiOty4KHe9nN6T-wmqf3x_ohuA6TcA@mail.gmail.com> <CAHPuVdU-1e_7KPH9JdSvbPn-tYptaXbHrQvQz=UEv+QJdseJxw@mail.gmail.com> <CAJE_bqdAuOns+1tjsXpyEsoaYHtcHH+=HSThMcjhUEkCX0gGxw@mail.gmail.com>
Date: Tue, 14 Jul 2015 13:13:23 -0400
Message-ID: <CAHPuVdW5x2+9kzWehztxFkes7fMTM_3TmpNy_5BotN55t3csxA@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary="001a11c13568af0a9e051ad8f4c0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/uWKCH9OuAb78wV4cn_GD9YtuzMw>
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
Reply-To: shuque@gmail.com
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: Tue, 14 Jul 2015 17:13:27 -0000

On Tue, Jul 14, 2015 at 1:00 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:

> At Mon, 13 Jul 2015 22:01:29 -0400,
> Shumon Huque <shuque@gmail.com> wrote:
>
> > 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, this will certainly be a very beneficial result of qname
> minimization.
>
> And the same remark should apply here, too.  We'd need "Stopping
> Downward Cache Search on NXDOMAIN" in addition to qname minimization
> for this to work.
>

I think we can distinguish the negative caching algorithm and the iterative
resolution algorithm.

The current iterative resolution algorithm already interprets NXDOMAIN
literally (unlike negative caching), so I don't think we need to explicitly
say this for the qname minimization variant of iterative resolution either.
However, I suppose there's no harm in adding explicit text around this
point.

Shumon Huque

v2.23.0 | Report a Bug | By Email