Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)

Joe Abley <jabley@hopcount.ca> Fri, 08 September 2017 11:52 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D328B13239C for <dnsop@ietfa.amsl.com>; Fri, 8 Sep 2017 04:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 qgCibGFvcmVE for <dnsop@ietfa.amsl.com>; Fri, 8 Sep 2017 04:52:22 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 85EB81321AA for <dnsop@ietf.org>; Fri, 8 Sep 2017 04:52:22 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id d16so5200285ioj.3 for <dnsop@ietf.org>; Fri, 08 Sep 2017 04:52:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d59GgZ1wtD20Zb8I0LYZBELCUDvNC7rKLxlsjJz2+vc=; b=oekw8NfgrAgW1hBPCyhC8Tmm3XhsoWMyrTm6ID5MWJwvJYGI+FrF3Rt3fnKJotnUPL cJHPY3Gj4KNbjooCveKoSQg7yz7xwFB7QXDI2r+P6dPa16A8x6ZTmbCv5RgaGYcs/GVs yAxmol6mN4+OGHL6sNe/uwma4rzHtJCLmiSdw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d59GgZ1wtD20Zb8I0LYZBELCUDvNC7rKLxlsjJz2+vc=; b=jnkp21lU6BQkUtA7LJ2i7GLeVh1+rMbOAivFf4E+CjSC2T3xCGNYAfosZNbGhz/puG BMkQm3q5ewLCGGX4w1JyhY8rCbbg03aO1LrXFW8Hi4TU/uUtLuTGUSSYpayVEqTodOZc 5v2en0SfBFC1w7PJ/mtIJX3ik1t3CGNe/cAmpFWvaDLnVXtz7Jq+edvjz/5FByQZ65Uh 1d720LX0yDTJD3YffsDOgn4InzruzbJvSyNv5AcKe7OWjkcMYlLr6qK+DyqE5z15PaM1 KKqopIfOxfpIjmogGbF4My5NtWrq7MXLtVjig7JhQ/vWKlCoXUK+O4TL641B5we3tTLR 472Q==
X-Gm-Message-State: AHPjjUh+eU/o8tXEDu+OeIJqnbgUIqXqRUKgib7boPCaUteBFhUj+QtO tWwYR3IuzANhcu7YkRdXhA==
X-Google-Smtp-Source: AOwi7QDnFXrRz8JcjuyZAH/AnlNaJb2WSvUyAgrH1D7PddVoKmoEF7bcRjY+RQjZfY9juHaztqH8Gg==
X-Received: by 10.107.31.13 with SMTP id f13mr3332586iof.12.1504871541449; Fri, 08 Sep 2017 04:52:21 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:101:3:7998:3c45:d081:29ee? (node-131dv4p2g4zfv5kbu6.ipv6.teksavvy.com. [2607:f2c0:101:3:7998:3c45:d081:29ee]) by smtp.gmail.com with ESMTPSA id m123sm942539iom.25.2017.09.08.04.52.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Sep 2017 04:52:20 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (14G60)
In-Reply-To: <8183111.Lxug4lBFgO@localhost.localdomain>
Date: Fri, 8 Sep 2017 07:52:19 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <33D02832-2E7E-4C99-980E-E20FE0E34E5B@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain>
To: Paul Vixie <paul@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jNkJ1s9GAgfYdXOyJgXosbsmtYA>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 11:52:24 -0000

> On Sep 8, 2017, at 01:28, Paul Vixie <paul@redbarn.org> wrote:
> 
> if they really need this, they should provide a method by which i can specify 
> both a TTL and an Expiry, and i will consider publishing both values, and if i 
> do, then they can use them the way i intend them. because as i said, autonomy. 
> it's my data, and my TTL.

Yes. That's a more succinct formulation of what I was trying to suggest.


Joe