Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?

Miek Gieben <miek@miek.nl> Tue, 08 May 2018 09:45 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 AA72A12D7E8 for <doh@ietfa.amsl.com>; Tue, 8 May 2018 02:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, 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 CEI7CJ8aREuy for <doh@ietfa.amsl.com>; Tue, 8 May 2018 02:45:49 -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 68D75120227 for <doh@ietf.org>; Tue, 8 May 2018 02:45:49 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id y15-v6so19877980wrg.11 for <doh@ietf.org>; Tue, 08 May 2018 02:45:49 -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:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=H7Q8zxm8ltb8OcwEqQwYRDH0XeBAPi5POkFPGqtxEtk=; b=vOvB+CwF5JSDWOq6UacbvHhuor7qFPdSr7v32pwmMqhqpLJNx9JHFrfRWkBBWPavKH IRxvRusjq+cM3jBzt52M63yrgL5vPbY9wzG5w5DtlN4CdxNu3kpiLEAuA5dxhLGWFYPs IWjQ1SsJ4QdG9P5xxS0Wn44s4OKq4sh4Kokh6FFhN0Ws1fvE1sxFmK1i+5Ccx42Aylbs P3moewiC68zNGxTsy0xOd4BsDu+usrl3ZtO2YTilrtLOGfPr2sjXfKrQL/QlL6Am1VZF U3ZCcMI7I+3DHAEddYo9LTOpcbL6+1NCMoE/SQlsiIToYjr90vsuyyvgteA++z6Z7hFv PlJg==
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 :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=H7Q8zxm8ltb8OcwEqQwYRDH0XeBAPi5POkFPGqtxEtk=; b=C+xiL6CxEFjZAMRRKgoFUjvqhda/4VjBTCzAkWwd4MGKtk/amRUeScZJxV6nK1+Gqm yfYesHvXlr6NojmucF/R0OLx+ryvlpPr5pqLeBA3LqmQzP2O3RyxhRts+fGybXwVLMtC jIe2KZb2gkDc+yBTM+udW1N5jpjY2q5oiCWmQ5Pjt+o2f5Nf0fU+dneDeyWwp2NTyfnU uQfM9FcLwzcygHL0Jrn5VTGXHYDL8v39YZKnrR2jlSRo0ub6qjkX00GtcOUsyUG57EQW M89/+n11aevo3vCk+jHND8d4ln+Vsc7xTreWR26cy2JdhjPpGd64ik+1f9eoG93wZR0h V2MA==
X-Gm-Message-State: ALQs6tBOCYl/utH7eo9YXRBnZaPrHkAdnZwtaQ8xh6asBb303YAVyPXV e8bVSjT4DDpYA/WEc+Zcu1imAtxg2D4=
X-Google-Smtp-Source: AB8JxZqs0rvnUe0Q6deLBLf95wtWD6moUPTCo9shSGgNIIO2VMHJO5AW0mLy1i229gTp2fYsxVryKw==
X-Received: by 2002:adf:9306:: with SMTP id 6-v6mr27030615wro.175.1525772747582; Tue, 08 May 2018 02:45:47 -0700 (PDT)
Received: from miek.nl ([2a01:7e00::f03c:91ff:fe79:234c]) by smtp.gmail.com with ESMTPSA id b57-v6sm39027953wra.9.2018.05.08.02.45.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 08 May 2018 02:45:46 -0700 (PDT)
Date: Tue, 8 May 2018 09:45:45 +0000
From: Miek Gieben <miek@miek.nl>
To: Mark Nottingham <mnot@mnot.net>
Cc: Paul Hoffman <paul.hoffman@icann.org>, DoH WG <doh@ietf.org>
Message-ID: <20180508094545.itl6cvpsekzrpxs4@miek.nl>
Mail-Followup-To: Mark Nottingham <mnot@mnot.net>, Paul Hoffman <paul.hoffman@icann.org>, DoH WG <doh@ietf.org>
References: <15A1809C-2CA3-4A3B-A5B1-279227C30223@icann.org> <3E34581E-E2DC-48B7-A4AD-6B9FDA418179@icann.org> <31900328-8813-47D3-9F89-0B863CE673B3@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <31900328-8813-47D3-9F89-0B863CE673B3@mnot.net>
User-Agent: Vim/Mutt/Linux
X-Home: http://www.miek.nl
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/MfOsOUeyjZ-JEbsxCwaCowax6-c>
Subject: Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
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: Tue, 08 May 2018 09:45:52 -0000

[ Quoting <mnot@mnot.net> in "Re: [Doh] [Ext] Does the HTTP fresh..." ]
>Proposal:
>
>Cache Interaction {#caching}

I like this text, but is the working-group OK with *not* mentioning DNSSEC?

If you only look a the TTL and not the inception and expiry dates of RRSIGs you 
can easily serve BAD data.

/Miek

--
Miek Gieben