Re: how many angels can dance on the head of a pin?

bmanning@vacation.karoshi.com Mon, 11 August 2008 16:39 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D5C13A6C06; Mon, 11 Aug 2008 09:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.066
X-Spam-Level:
X-Spam-Status: No, score=-101.066 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuEVNiKrHgj3; Mon, 11 Aug 2008 09:39:32 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 35A603A6BBE; Mon, 11 Aug 2008 09:39:32 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KSaHD-0001ma-Sj for namedroppers-data@psg.com; Mon, 11 Aug 2008 16:29:47 +0000
Received: from [2001:478:6:0:230:48ff:fe11:220a] (helo=vacation.karoshi.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <bmanning@karoshi.com>) id 1KSaH9-0001US-6x for namedroppers@ops.ietf.org; Mon, 11 Aug 2008 16:29:45 +0000
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id m7B2qnIP003220; Mon, 11 Aug 2008 02:52:49 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id m7B2qgr8003219; Mon, 11 Aug 2008 02:52:42 GMT
Date: Mon, 11 Aug 2008 02:52:42 +0000
From: bmanning@vacation.karoshi.com
To: Duane at e164 dot org <duane@e164.org>
Cc: bmanning@vacation.karoshi.com, Namedroppers <namedroppers@ops.ietf.org>
Subject: Re: how many angels can dance on the head of a pin?
Message-ID: <20080811025242.GA3158@vacation.karoshi.com.>
References: <200808080237.m782bBqk005628@drugs.dv.isc.org> <489BBA1C.1040107@e164.org> <489E4D44.1080306@links.org> <20080810042136.GA18568@vacation.karoshi.com.> <489E89B6.6090208@e164.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <489E89B6.6090208@e164.org>
User-Agent: Mutt/1.4.1i
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

> >>>> 	Well we could stop caching any DNS data.  That's the only
> >>>> 	way to make it match the credit card industry model where
> >>>> 	changes are instantly available.
> > 
> > 
> > 	these days, i am thinking Mark is just baiting trolls.
> > 	caches are too useful to abandon outright, but i'm pretty sure
> > 	rethinking them is a great idea.
> 
> Caches seem to be the majority of concern in the last 3 to 4 weeks, I
> doubt anyone would disagree they can be useful just like web caching can
> be useful.
> 
> The question is does the pros outweigh the cons?
> 
> If shared caching at the ISP level is abandoned in favour of moving them
> closer to the end user, either on their computer or on the LAN but isn't
> accessible usually from beyond the LAN, would that not solve the
> majority of concerns currently being expressed?
> 
> -- 
> 
> Best regards,
>  Duane


	if your caching at all (near/far) your caching.
	if you keep zero state "...stop caching any DNS data... (Mark Andrews)"
	then you are not.

	my gentle assertion was that caching is valuable, should be kept/rethought.
	theevents of the day are only tangential to cache design.  -IF- caching is
	to be re-thought, then it should be carefully thought out, not a twitch
	reaction to a (perceived) threat.


--bill

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>