Re: [DNSOP] Last Call: <draft-ietf-dnsop-resolver-priming-09.txt> (Initializing a DNS Resolver with Priming Queries) to Best Current Practice

"Paul Hoffman" <paul.hoffman@vpnc.org> Sun, 13 November 2016 12:43 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA22412948C for <ietf@ietfa.amsl.com>; Sun, 13 Nov 2016 04:43:45 -0800 (PST)
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] 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 EYsMAGeqRpuB for <ietf@ietfa.amsl.com>; Sun, 13 Nov 2016 04:43:44 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 7FD891293D8 for <ietf@ietf.org>; Sun, 13 Nov 2016 04:43:44 -0800 (PST)
Received: from [10.32.60.39] ([211.44.215.72]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id uADChTxS018221 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Sun, 13 Nov 2016 05:43:35 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host [211.44.215.72] claimed to be [10.32.60.39]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: ietf@ietf.org
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-resolver-priming-09.txt> (Initializing a DNS Resolver with Priming Queries) to Best Current Practice
Date: Sun, 13 Nov 2016 21:43:37 +0900
Message-ID: <260DA064-A1B9-478C-9CBA-6545D8B6E992@vpnc.org>
In-Reply-To: <CACfw2hgdRw+VAVAX2RFFF9uhYz7JsLihSJ5RQWBaPg3txmbXqw@mail.gmail.com>
References: <147758022943.24671.1643494998130945117.idtracker@ietfa.amsl.com> <CACfw2hgdRw+VAVAX2RFFF9uhYz7JsLihSJ5RQWBaPg3txmbXqw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bUqfmxzBBvHGxo-QPqX-19vp0LA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Nov 2016 12:43:46 -0000

On 3 Nov 2016, at 21:16, william manning wrote:

> What method is in place to ensure that the cache is, #1, checked 
> before
> emitting priming queries, #2, that if there is already data (complete 
> or
> partial) in the cache, how is the client supposed to determine if the
> cached data is preferred over unverified, remote data?  Or does the 
> client
> operate with the presumption that local data is always wrong and the 
> best
> data is always external?
>
> Inquiring Minds want to know.

There is no such method in place. This document describes how to prime 
resolvers and when you should, but does not prohibit any other use of 
the same DNS queries when priming is not needed.

--Paul Hoffman