IETF Logo Mail Archive

Re: [Doh] meta qtypes

Miek Gieben <miek@miek.nl> Mon, 19 March 2018 09:49 UTC

Return-Path: <miek@miek.nl>
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 CC19E1270B4 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 02:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.com
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 wW4DZFxgwX4H for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 02:49:16 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27755127010 for <doh@ietf.org>; Mon, 19 Mar 2018 02:49:16 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id o8so17924477wra.1 for <doh@ietf.org>; Mon, 19 Mar 2018 02:49:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=2tRM2t0FEgzfzp/17hWew7SEfzQFklGfxxAw+22wbAA=; b=BVN98XZkCpz3SOZYtkYxfgw6zD7ApseYjPiOriZ8iPmeml4AOJcV1uUoWcC+G7bLbw epE6vvKmxV37Loud5eGOUS3166xlVBb59Cx5fw0EoDvpxXZSxzbjwUq+tqbtCa2vZERb Q+gk1oI36W24UWRkGW7QAifdUbKhrIF0b8lCTxMAFv6oxwGAxC/6IzTpAXMDy41RrvlM DbarIKdoYR2rRf+265Uj91kHYLwcimkaC5PZGn9Y6a1tNicyHJz0uSJw2beE+apN+ipp 34JJ6oZ+jbhjh3uqi03T458oIXciBD3jTmzAqwWirAN45DPw+S+oHy5BInfFqQWhdpcx 7CLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2tRM2t0FEgzfzp/17hWew7SEfzQFklGfxxAw+22wbAA=; b=ZBkneS8lt+EwijJkqOlpxPewNpEzyx8RLYTGayUa7iutoB9Iy3rbs0NEfY+cr4s8NU OaDiDIZql356zx8SbC2btbReNDhGeMA6qgj8QWc6wBMjYZxglFmiQmgYfM1a2K0grbUv TOhEWEEmRF35OGWfUpjoSF3dFVfCgPsDocPl9hOGcEc1ZeZ0lQjQqf6sqKMlSPontU9x I0C97ivu4ccor2WOSaPteBzup5sJWX3bJxDd49kWHEHhGblF5q5dWXNxuv4pYHaubIDj SjsuWTKoRBjIkiBtrGh5DsKiIMh1mfJu15YWwXn5YBLENLeZ1BZDZwH8WR++vLVN9Y3P 7HdA==
X-Gm-Message-State: AElRT7FNYHz5nZkNbvzX1YJLR2sESRnjeQWIe8yFSPixQ5dWRWMD59xb zOQ+6IqexCjzX7b8j10k+xZ5Fw==
X-Google-Smtp-Source: AG47ELsskNhzmFaB12bjLdMm/iYiv9ZRePGVWE7gvhSFixNC7LP7XbQQ5ICp2+xO+SWeUIrulSkLtQ==
X-Received: by 10.223.131.37 with SMTP id 34mr9128889wrd.169.1521452954566; Mon, 19 Mar 2018 02:49:14 -0700 (PDT)
Received: from miek.nl ([2a01:7e00::f03c:91ff:fe79:234c]) by smtp.gmail.com with ESMTPSA id z3sm12289130wme.3.2018.03.19.02.49.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Mar 2018 02:49:13 -0700 (PDT)
Date: Mon, 19 Mar 2018 09:49:12 +0000
From: Miek Gieben <miek@miek.nl>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Patrick McManus <pmcmanus@mozilla.com>, DoH WG <doh@ietf.org>
Message-ID: <20180319094912.46fts2zxxlk6o2jx@miek.nl>
References: <20180318143811.bn5kwr7oqo2ux6qm@miek.nl> <CAOdDvNoNN98zOuPAepS0=0Nt06+UAGV1ZCrxs0J2TzQaVnJz8w@mail.gmail.com> <20180318190804.5mgxarazepfut56i@miek.nl> <20180319091634.GC16151@laperouse.bortzmeyer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <20180319091634.GC16151@laperouse.bortzmeyer.org>
User-Agent: Vim/Mutt/Linux
X-Home: http://www.miek.nl
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/09D50sRrptHviDYxwZ2z907ZMTg>
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: Mon, 19 Mar 2018 09:49:18 -0000

[ Quoting <bortzmeyer@nic.fr> in "Re: [Doh] meta qtypes..." ]
>> I think this draft should say "MUST not cache these responses".
>
>I have a less radical proposal:
>
>"DoH servers SHOULD return a Cache-Control header (RFC 7234, section
>5.2.2). They MAY send "Cache-control: no-cache" in all cases [if
>they're lazy]. For positive
>answers (ANCOUNT>0), if the DoH server returns "Cache-control:
>max-age=N", the maximum age MUST be the TTL of the answer seen by the
>Doh server. For negative answers (NXDOMAIN), if the DoH server returns "Cache-control:
>max-age=N", the maximum age MUST be calculated from the SOA record of
>the zone (RFC 2308, section 3) [note it allows a server to return
>"Cache-control: no-cache" only for NXDOMAIN]"

I agree that this works (but still leaves out RRSIGs).

The (major) downside is that a DoH server doesn't just ship bytes anymore; it 
need to fully inspect the payload to make an informed cache TTL decision.

Note: I'm fine with either - nocache or something along the lines Stephane 
proposes.

/Miek

--
Miek Gieben

v2.23.0 | Report a Bug | By Email