IETF Logo Mail Archive

Re: [DNSOP] Working Group Last Call draft-ietf-dnsop-resolver-priming

Andreas Gustafsson <gson@araneus.fi> Sat, 13 August 2016 11:01 UTC

Return-Path: <gson@gson.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A7912B047 for <dnsop@ietfa.amsl.com>; Sat, 13 Aug 2016 04:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 NC8ok4uy7Kgp for <dnsop@ietfa.amsl.com>; Sat, 13 Aug 2016 04:01:55 -0700 (PDT)
Received: from gusto.araneus.fi (gusto.araneus.fi [185.55.84.130]) by ietfa.amsl.com (Postfix) with ESMTP id C103812D126 for <dnsop@ietf.org>; Sat, 13 Aug 2016 04:01:54 -0700 (PDT)
Received: from guava.gson.org (unknown [10.0.1.240]) by gusto.araneus.fi (Postfix) with ESMTP id 1257C8BE305; Sat, 13 Aug 2016 11:01:53 +0000 (UTC)
Received: by guava.gson.org (Postfix, from userid 101) id 45E8A7446B8; Sat, 13 Aug 2016 14:01:52 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <22446.65056.67787.126514@guava.gson.org>
Date: Sat, 13 Aug 2016 14:01:52 +0300
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: Re: <B0ED30A0-707B-4E07-88F3-37385CC684C4@vpnc.org>
References: <f8c62b82-258c-2b2b-5186-c3cd8e7d7448@gmail.com> <20160805114511.3ab76c8e@pallas.home.time-travellers.org> <B0ED30A0-707B-4E07-88F3-37385CC684C4@vpnc.org>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
From: Andreas Gustafsson <gson@araneus.fi>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/k1cCJPqo2tsf7yigGF_Enh6jE4A>
Cc: Shane Kerr <shane@time-travellers.org>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Working Group Last Call draft-ietf-dnsop-resolver-priming
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Aug 2016 11:01:57 -0000

On Wednesday, Paul Hoffman wrote:
> > The "2 seconds" seems a bit arbitrary.
> 
> Yep. But...
> 
> > I'm not sure why any
> > recommendations need to be made at all. The document already says that
> > these are basically normal DNS queries elsewhere - surely that is 
> > enough?
> 
> The queries are normal, but the reliance on them is not. Without 
> priming, nothing can be answered, so that makes them kinda special.

It's not necessarily the case that nothing can be answered.
Resolvers can and do resolve user queries using the configured root
servers while priming is in progress.

There is nothing wrong with existing resolvers that use the same
timeout and retransmission strategies for priming queries as for any
other query, and it seems wrong to me that a specific retransmission
timeout should be required for some queries but not others.
-- 
Andreas Gustafsson, gson@araneus.fi

v2.23.0 | Report a Bug | By Email