IETF Logo Mail Archive

Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt

Phil Regnauld <regnauld@nsrc.org> Thu, 04 July 2013 10:57 UTC

Return-Path: <regnauld@x0.dk>
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 92BD521F9E72 for <dnsop@ietfa.amsl.com>; Thu, 4 Jul 2013 03:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNYecR165Q3I for <dnsop@ietfa.amsl.com>; Thu, 4 Jul 2013 03:57:14 -0700 (PDT)
Received: from moof.catpipe.net (moof.catpipe.net [194.28.252.64]) by ietfa.amsl.com (Postfix) with ESMTP id A72C621F9E6D for <dnsop@ietf.org>; Thu, 4 Jul 2013 03:57:13 -0700 (PDT)
Received: from localhost (moof.catpipe.net [194.28.252.64]) by localhost.catpipe.net (Postfix) with ESMTP id 281AD4CE9F7; Thu, 4 Jul 2013 12:57:12 +0200 (CEST)
Received: from moof.catpipe.net ([194.28.252.64]) by localhost (moof.catpipe.net [194.28.252.64]) (amavisd-new, port 10024) with ESMTP id De2FKJRnv50Q; Thu, 4 Jul 2013 12:57:11 +0200 (CEST)
Received: from macbook.bluepipe.net (macbook.bluepipe.net [195.249.214.179]) (Authenticated sender: relayuser) by moof.catpipe.net (Postfix) with ESMTPA id B2B004CE996; Thu, 4 Jul 2013 12:57:11 +0200 (CEST)
Received: by macbook.bluepipe.net (Postfix, from userid 1001) id 58B659B161D; Thu, 4 Jul 2013 12:57:13 +0200 (CEST)
Date: Thu, 04 Jul 2013 12:57:13 +0200
From: Phil Regnauld <regnauld@nsrc.org>
To: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
Message-ID: <20130704105713.GC59704@macbook.bluepipe.net>
References: <20130703210147.69996.qmail@joyce.lan> <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org> <FAFC3938-13F8-44FD-8AD9-5D71D68E1A1A@kumari.net> <51D53167.9090906@nlnetlabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <51D53167.9090906@nlnetlabs.nl>
X-Operating-System: Darwin 12.4.0 x86_64
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 04 Jul 2013 10:57:20 -0000

W.C.A. Wijngaards (wouter) writes:
> 
> Yes I wrote the code and say so.  (Not sure how that is better than
> reading the source).  Results, anecdotally, are very modest.  It does
> remove latency spikes for popular names.

	What does the latency spike translate to in terms of extra traffic
	(clients) ? A thundering herd effect ? Congestion ? Considering
	how many tricks modern browsers have up their sleeves (including
	prefetching data linked on a page), I'm wondering how the two
	interact. I've always mentioned the expiring RR prefetch option
	to be a cool feature of Unbound, but in reality, what does it mean
	for users ?

> Aside, I agree that prefetching before the TTL expires is overly
> aggressive.

	If it mitigates other issues...

> But lengthening the TTL is worse (for DNSSEC rollovers
> TTLs MUST expire, or the signatures become bogus).

	:)

	P.

v2.23.0 | Report a Bug | By Email