Re: [Doh] meta qtypes

Patrick McManus <pmcmanus@mozilla.com> Sun, 18 March 2018 19:47 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F237129C59 for <doh@ietfa.amsl.com>; Sun, 18 Mar 2018 12:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.101
X-Spam-Level: **
X-Spam-Status: No, score=2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SBL_CSS=3.335, 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 CZY-VklVl0UG for <doh@ietfa.amsl.com>; Sun, 18 Mar 2018 12:47:56 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD6D126D73 for <doh@ietf.org>; Sun, 18 Mar 2018 12:47:56 -0700 (PDT)
Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com [209.85.218.42]) by linode64.ducksong.com (Postfix) with ESMTPSA id E3AB53A019 for <doh@ietf.org>; Sun, 18 Mar 2018 15:47:55 -0400 (EDT)
Received: by mail-oi0-f42.google.com with SMTP id 71so1238334oie.12 for <doh@ietf.org>; Sun, 18 Mar 2018 12:47:55 -0700 (PDT)
X-Gm-Message-State: AElRT7Fmi/snq8HLfL1xvhW81pdHuIZkBo50BVXHXOqnuYiq7LEOJRdU mOiKaGjuUYhu9kVp/cp9tGj3+TSYV8nRaM6BcOc=
X-Google-Smtp-Source: AG47ELvRr6Au9L893roDmE2vFR2hN9BZkNvyQeUfv3jhG4ft/OXmyRJL/0K+d3wpmvDsAqfzF+XwUpurRh+5ZiWEw84=
X-Received: by 10.202.3.198 with SMTP id 189mr5282653oid.132.1521402475550; Sun, 18 Mar 2018 12:47:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.66.212 with HTTP; Sun, 18 Mar 2018 12:47:54 -0700 (PDT)
Received: by 10.74.66.212 with HTTP; Sun, 18 Mar 2018 12:47:54 -0700 (PDT)
In-Reply-To: <20180318190804.5mgxarazepfut56i@miek.nl>
References: <20180318143811.bn5kwr7oqo2ux6qm@miek.nl> <CAOdDvNoNN98zOuPAepS0=0Nt06+UAGV1ZCrxs0J2TzQaVnJz8w@mail.gmail.com> <20180318190804.5mgxarazepfut56i@miek.nl>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Sun, 18 Mar 2018 19:47:54 +0000
X-Gmail-Original-Message-ID: <CAOdDvNqH02Wedk=ep+0t0SyCdOZQ2+rQx+gp4S8OyeakrDUJUg@mail.gmail.com>
Message-ID: <CAOdDvNqH02Wedk=ep+0t0SyCdOZQ2+rQx+gp4S8OyeakrDUJUg@mail.gmail.com>
To: DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c0463c1d9d2a0567b51e07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/nBIgRu8OUSlEZi8jRCHyhZKg9wY>
Subject: Re: [Doh] meta qtypes
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 19:47:58 -0000

Section 4 has spme rules about generating http freshness lifetimes from dns
responses. Is there a text change to that you are proposing?

On Mar 18, 2018 7:08 PM, "Miek Gieben" <miek@miek.nl> wrote:

> [ Quoting <pmcmanus@mozilla.com> in "Re: [Doh] meta qtypes..." ]
>
>> Hi - DoH itself doesn't require axfr/etc anywhere that DNS would not (I'm
>> not aware of whether it does or not) - the text is just meant to give the
>> HTTP considerations when it does carry larger DNS responses such as that.
>>
>> WRT HTTP caching - section 4 of DoH talks about how HTTP freshness
>> lifetimes should be set for DoH responses. Is there something different
>> here?
>>
>
> This HTTP caching opens up a pretty big can of worms on what to set the
> cache
> TTL to.
>
> If we consider HTTP/2 *just* the transport than it should not be concerned
> with
> caching (i.e. TCP doesn't cache).
>
> If we do want to cache on this layer a server implementing DoH needs to
> inspect the DNS packet, it should (among other things), look for a SOA
> record to get a TTL or MINTTL, or get the minimum TTL of all the records in
> the message, or look for RRSIG expiration times and distill a minimum TTL
> from those.
>
> I think this draft should say "MUST not cache these responses".
>
> /Miek
>
> --
> Miek Gieben
>