Re: [dnsoverhttp] Caching model
Patrick McManus <pmcmanus@mozilla.com> Tue, 31 October 2017 06:28 UTC
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: dnsoverhttp@ietfa.amsl.com
Delivered-To: dnsoverhttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D04DFB77 for <dnsoverhttp@ietfa.amsl.com>; Mon, 30 Oct 2017 23:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level:
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.665] autolearn=no 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 yK0JGbgNW41q for <dnsoverhttp@ietfa.amsl.com>; Mon, 30 Oct 2017 23:28:46 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 37F0713F5DE for <dnsoverhttp@ietf.org>; Mon, 30 Oct 2017 23:28:46 -0700 (PDT)
Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) by linode64.ducksong.com (Postfix) with ESMTPSA id F325E3A2A1 for <dnsoverhttp@ietf.org>; Tue, 31 Oct 2017 02:28:42 -0400 (EDT)
Received: by mail-lf0-f51.google.com with SMTP id 90so17653382lfs.13 for <dnsoverhttp@ietf.org>; Mon, 30 Oct 2017 23:28:42 -0700 (PDT)
X-Gm-Message-State: AMCzsaW/5LnArUzpqBncvcKN/1/KxzNaQEglE4l0dnv5aRDSosmidYA8 VDjH0DHwxbDNlWJxkjWuutHTWq3tdFkGwGZBxgE=
X-Google-Smtp-Source: ABhQp+S7BVA/Bg/JAFVWnPsfwfVe/DLgX82gX/q6q6Lai+w4EpnS2U2s9SNWTRFyVWL8HL1DcQeAL7o6yainzKksoNE=
X-Received: by 10.46.56.20 with SMTP id f20mr414547lja.189.1509431321654; Mon, 30 Oct 2017 23:28:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.21.22 with HTTP; Mon, 30 Oct 2017 23:28:40 -0700 (PDT)
In-Reply-To: <CABkgnnU_5Q6BOxf+HzpuCSkb8OG5i0sgqyF9UEr9VRyDvd5s7w@mail.gmail.com>
References: <CABkgnnU_5Q6BOxf+HzpuCSkb8OG5i0sgqyF9UEr9VRyDvd5s7w@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 31 Oct 2017 02:28:40 -0400
X-Gmail-Original-Message-ID: <CAOdDvNofVo-gjoqP1HamMTnDqasHQ_Aikhp-M-_TtLNeqVGERw@mail.gmail.com>
Message-ID: <CAOdDvNofVo-gjoqP1HamMTnDqasHQ_Aikhp-M-_TtLNeqVGERw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "dnsoverhttp@ietf.org" <dnsoverhttp@ietf.org>
Content-Type: multipart/alternative; boundary="089e0823e0b4bd7b91055cd1dd9b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsoverhttp/8LlZ94NNZRufDUj8PUc3G4pDd9g>
Subject: Re: [dnsoverhttp] Caching model
X-BeenThere: dnsoverhttp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of DNS over HTTP <dnsoverhttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsoverhttp/>
List-Post: <mailto:dnsoverhttp@ietf.org>
List-Help: <mailto:dnsoverhttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 06:28:48 -0000
I think the HTTP cache fundamentally plays a role as a shared cache between multiple clients. Mark draws that picture with a CDN, which is one possibility. Another is the javascript use case where the client DNS cache may not exist or even if it does exist the shared cache plays the role of heirarchical cache.. to whatever extent different first parties can share http cache entries they can share doh entries. in the case where this is a straight line, then it makes sense to disable one of the two client side caches.. note that its common to have a http cache that also stores a bunch of post-processed stuff linked to the http cache entry.. firefox has done/does/will do that with a bunch of things already (raster formats, javascript parsing, wasm ..) and some kind of parsed dns record that allowed disabling the standalone dns cache would seem likely. On Sunday, October 29, 2017, Martin Thomson <martin.thomson@gmail.com> wrote: > See https://github.com/paulehoffman/draft-ietf-doh- > 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 > dnsoverhttp@ietf.org <javascript:;> > https://www.ietf.org/mailman/listinfo/dnsoverhttp >
- [dnsoverhttp] Caching model Martin Thomson
- Re: [dnsoverhttp] Caching model Ian Swett
- Re: [dnsoverhttp] [Ext] Caching model Paul Hoffman
- Re: [dnsoverhttp] [Ext] Caching model Martin Thomson
- Re: [dnsoverhttp] Caching model Mark Nottingham
- Re: [dnsoverhttp] [Ext] Caching model Paul Hoffman
- Re: [dnsoverhttp] [Ext] Caching model Martin Thomson
- Re: [dnsoverhttp] [Ext] Caching model Ben Schwartz
- Re: [dnsoverhttp] [Ext] Caching model Mark Nottingham
- Re: [dnsoverhttp] Caching model Patrick McManus
- Re: [dnsoverhttp] [Ext] Caching model Erik Kline