Re: [DNSOP] Fwd: New Version Notification for draft-muks-dnsop-dns-thundering-herd-00.txt

Paul Wouters <paul@nohats.ca> Thu, 25 June 2020 18:29 UTC

Return-Path: <paul@nohats.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 DB6013A0E7C for <dnsop@ietfa.amsl.com>; Thu, 25 Jun 2020 11:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.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 rXPfnZI5FKWK for <dnsop@ietfa.amsl.com>; Thu, 25 Jun 2020 11:29:09 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83F0F3A0E71 for <dnsop@ietf.org>; Thu, 25 Jun 2020 11:29:09 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49t7nt48ftzFgW; Thu, 25 Jun 2020 20:29:06 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1593109746; bh=rLDC0/0hzvBSn0A3ULjvLsEiktqXs6UHNIMuUc7XEiA=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=AgKt1FbuUKjDnZHnmU8GCzj0p9tqi0hUSfWQmrGFs4XGTFLrgJR9xccHZKf19TnDm 5ZDB+yzYv/uKa3SNeEMZHRYwfW/XYn5emFkhDApaBfqniRPzD7Pnneqhi5EXTqIOPx mnexPkPOhPxyoA/tSeexKRGsm60kNEbKJNQdBxh0=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id eJ1jNOe2RxLN; Thu, 25 Jun 2020 20:29:05 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 25 Jun 2020 20:29:04 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id B003B6029B9B; Thu, 25 Jun 2020 14:29:03 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id A61A666B7C; Thu, 25 Jun 2020 14:29:03 -0400 (EDT)
Date: Thu, 25 Jun 2020 14:29:03 -0400
From: Paul Wouters <paul@nohats.ca>
To: Mukund Sivaraman <muks@mukund.org>
cc: dnsop@ietf.org, Cricket Liu <cricket@infobox.com>
In-Reply-To: <20200625165049.GA22173@jurassic.vpn.mukund.org>
Message-ID: <alpine.LRH.2.22.394.2006251428010.18151@bofh.nohats.ca>
References: <159310275958.28219.2228183649424027878@ietfa.amsl.com> <20200625165049.GA22173@jurassic.vpn.mukund.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/GMMgm4rK6QJllZu1Zv2xQMg_OZM>
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: Thu, 25 Jun 2020 18:29:15 -0000

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.

Paul