Re: [dnsoverhttp] Caching model

Ian Swett <> Mon, 30 October 2017 01:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BDE631394EB for <>; Sun, 29 Oct 2017 18:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mnN7XJcYjThN for <>; Sun, 29 Oct 2017 18:54:18 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2049313FD4D for <>; Sun, 29 Oct 2017 18:54:18 -0700 (PDT)
Received: by with SMTP id 101so23772688ioj.3 for <>; Sun, 29 Oct 2017 18:54:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3uVt5zpDMlGzoYRBKGv4NGj9LBd3dxNpyi0A8OVDtC8=; b=Ofwyqs+2BJauF2syirxQHrWelwblrqcrsamPJCulEKenEHp9aFDjpSkfnvqdptCreH rz06x1NQUkOJVFBiNywD5beUSaBqbvk4wQGNnW6psGtlkAyz5WGB8g1na49R2T0BQj0w hDSxgmEJmrjQsLuRtY7Lzq1V6dd35v7cGabIKS+Z+Rn6VgmRJmTRI6Xpk9NOtF4W7OvA hAhRiutNJfQETr8fQWNFtNSgOyZ70vH2G2We8no5P4rPpB2J46KPDw/Odp06puEj0rpk RXBnMsk3Iotp0/Mz3GyL2phfwb6wj+EfNXc21z8FuT++C4638OEUEqEtQrZDilcARawd Bq0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3uVt5zpDMlGzoYRBKGv4NGj9LBd3dxNpyi0A8OVDtC8=; b=QD2XUsH93WwWvpPNAtvIMIK/fF0NZjPXtmHorX+DhWT1j6yx6BHkN782Z5AxQLlMuB 4KcCxT8wGm4hYai82mNBDec1SX4HQZYOoVIhQe7rZ0oXqagd+LQo1CCG8ue0ZEobIlLD hGB3yqT9aGfywdFJNbRjyz983mLzIqb3qLoOce+HZD3QG+/9/pNlm5BLII4Kj1K7GhBN CY3eaW5IAIHlo0nJOyGI64K36DznPCq5cwzZQBGnU/7S+9G9am+URnXXWBk5GuOwpYMK ywsoQPcjE0jWt5hoHvaKR8U1XmxrIVmfH1tV6FYQmRR1qo16Fx/j+0dBixUTBJvZObRL bxWA==
X-Gm-Message-State: AMCzsaV5BhiUHsJFsuEOpdw/uHX4Fq+qagNS9+jid3NzJaMh1qmg+DtW szcYshraichL1rRZfpguAbRUmcitSSg/qMHWKkRWxiAM
X-Google-Smtp-Source: ABhQp+QJZv0tzIBZviyCXSPJZw5JqL8JtYHsEMooRQGoiUbOMSaZcymAf1EC7cj4ako+txr0qJpA53eymGbb45DCS6o=
X-Received: by with SMTP id p130mr4260789itc.54.1509328457198; Sun, 29 Oct 2017 18:54:17 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sun, 29 Oct 2017 18:53:56 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Ian Swett <>
Date: Sun, 29 Oct 2017 21:53:56 -0400
Message-ID: <>
To: Martin Thomson <>
Content-Type: multipart/alternative; boundary="001a114ab8e48ac10e055cb9eac0"
Archived-At: <>
Subject: Re: [dnsoverhttp] Caching model
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of DNS over HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Oct 2017 01:54:21 -0000

I assumed HTTP caching would either be disabled or closely integrated with
the DNS resolver's TTL.  Both seem viable, but disabling HTTP caching seems

On Sun, Oct 29, 2017 at 9:36 PM, Martin Thomson <>

> See
> dns-over-https/issues/14
> and several others.
> My request is that we agree on what the model is, then we can talk
> about the properties we can extract from that.
> My understanding is that the DNS client would consult its local stack
> and that stack would use HTTP to talk to a DNS API server.  In that
> model, there are at least three caches in play: the local DNS resolver
> cache, the HTTP cache and the DNS API server cache.
> If those caches are ordered as I describe, and the two DNS caches are
> driven based on the TTL, I'm struggling to find a role for the HTTP
> cache.  There are things that HTTP can do with caching that would be
> nice, but I'm not seeing any way to really access HTTP caching
> features in that architecture.
> It's a little unfortunate, but in that architecture it would probably
> be better to disable HTTP caching entirely.  HTTP caching has a bunch
> of features that are more flexible, but if that caching is wedged
> between two relatively inflexible caches, it won't have any
> opportunity to add value.
> _______________________________________________
> dnsoverhttp mailing list