Re: [DNSOP] Fwd: New Version Notification for draft-muks-dnsop-dns-thundering-herd-00.txt
Paul Vixie <paul@redbarn.org> Fri, 26 June 2020 01:02 UTC
Return-Path: <paul@redbarn.org>
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 541E63A10B7
for <dnsop@ietfa.amsl.com>; Thu, 25 Jun 2020 18:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham 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 SwhuwoiDitNr for <dnsop@ietfa.amsl.com>;
Thu, 25 Jun 2020 18:02:54 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 47A5A3A1046
for <dnsop@ietf.org>; Thu, 25 Jun 2020 18:02:54 -0700 (PDT)
Received: from linux-9daj.localnet (dhcp-166.access.rits.tisf.net
[24.104.150.166])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256)
(Client did not present a certificate)
by family.redbarn.org (Postfix) with ESMTPSA id C164EB0588;
Fri, 26 Jun 2020 01:02:51 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Mukund Sivaraman <muks@mukund.org>, dnsop@ietf.org
Cc: Cricket Liu <cricket@infobox.com>, dnsop@ietf.org,
Paul Wouters <paul@nohats.ca>
Date: Fri, 26 Jun 2020 01:02:51 +0000
Message-ID: <1825040.HPJnnLGoiM@linux-9daj>
Organization: none
In-Reply-To: <alpine.LRH.2.22.394.2006251428010.18151@bofh.nohats.ca>
References: <159310275958.28219.2228183649424027878@ietfa.amsl.com>
<20200625165049.GA22173@jurassic.vpn.mukund.org>
<alpine.LRH.2.22.394.2006251428010.18151@bofh.nohats.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5rBRLkQDGWo_cj9EFLP0HZPk3Gg>
Subject: Re: [DNSOP] Fwd: New Version Notification for
draft-muks-dnsop-dns-thundering-herd-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Jun 2020 01:02:55 -0000
On Thursday, 25 June 2020 18:29:03 UTC Paul Wouters wrote: > On Thu, 25 Jun 2020, Mukund Sivaraman wrote: > > For whoever is interested, this is a description of a pattern of queries > > noticed at busy public resolvers that has led to issues in at least 4 > > different sites in the last 2 months. > > > > The current revision is a work in progress. We are still developing some > > mitigations for NIOS, and some more introductory text also has to be > > added. > > I would add a more explicit section on using prefetching of frequently > asked queries, which mitigates (eliminates) the period when an answer is not > available in the cache. i'm sorry in advance for anybody who is now hearing this for the 100th time. please don't pre-fetch. feel free to pre-discard; TTL is a maximum, and if you want to randomly subtract from TTL upon every reuse, you'll remain compliant. if the data turns out to be important it'll return. but prospective pre-fetch means you may be creating network load for no purpose -- the data may not come back again, or if it does, it may have changed, in which case you don't want the stale stuff that pre-fetch would have brought you. this solves the thundering herd problem but without creating new problems. the goal is de-synchronization. random subtractions to TTL in cache accomplishes it. -- Paul
- [DNSOP] Fwd: New Version Notification for draft-m… Mukund Sivaraman
- Re: [DNSOP] Fwd: New Version Notification for dra… Paul Wouters
- Re: [DNSOP] Fwd: New Version Notification for dra… dagon
- Re: [DNSOP] Fwd: New Version Notification for dra… Robert Edmonds
- Re: [DNSOP] Fwd: New Version Notification for dra… Paul Wouters
- Re: [DNSOP] Fwd: New Version Notification for dra… Paul Vixie
- Re: [DNSOP] Fwd: New Version Notification for dra… Mukund Sivaraman
- Re: [DNSOP] Fwd: New Version Notification for dra… Mukund Sivaraman
- Re: [DNSOP] Fwd: New Version Notification for dra… Mukund Sivaraman