Re: [DNSOP] AS112 for TLDs

bmanning@vacation.karoshi.com Fri, 04 April 2008 15:57 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@optimus.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFBA73A6DDD; Fri, 4 Apr 2008 08:57:46 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9FCE3A6CCB for <dnsop@core3.amsl.com>; Fri, 4 Apr 2008 08:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 a1pjRl0H1w0g for <dnsop@core3.amsl.com>; Fri, 4 Apr 2008 08:57:45 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by core3.amsl.com (Postfix) with ESMTP id 849173A6899 for <dnsop@ietf.org>; Fri, 4 Apr 2008 08:57:44 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id m34FugqM015533; Fri, 4 Apr 2008 15:56:42 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id m34FucCt015532; Fri, 4 Apr 2008 15:56:38 GMT
Date: Fri, 04 Apr 2008 15:56:38 +0000
From: bmanning@vacation.karoshi.com
To: David Conrad <drc@virtualized.org>
Message-ID: <20080404155638.GA15372@vacation.karoshi.com.>
References: <20080404025908.GA6781@vacation.karoshi.com.> <200804040316.m343GWNE061906@drugs.dv.isc.org> <20080404140210.GJ1184@commandprompt.com> <34168149-621F-497C-BCE7-01F68F1B2889@virtualized.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <34168149-621F-497C-BCE7-01F68F1B2889@virtualized.org>
User-Agent: Mutt/1.4.1i
Cc: dnsop@ietf.org, Andrew Sullivan <ajs@commandprompt.com>
Subject: Re: [DNSOP] AS112 for TLDs
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

On Fri, Apr 04, 2008 at 07:37:31AM -0700, David Conrad wrote:
> On Apr 4, 2008, at 7:02 AM, Andrew Sullivan wrote:
> > On Fri, Apr 04, 2008 at 02:16:32PM +1100, Mark Andrews wrote:
> >>> 	er, it (the bogus ttraffic) still reaches the root.
> >>> 	just your copy of the root, not mine.
> >> 	Yep.  This should be seen as a good thing.  The information
> >> 	leakage to the root servers is enormous.
> > This sounds to me like a cure that is quite possibly worse than the
> > disease.
> 
> In what way?

	Mark made the claim that a local copy of the root would stop the
	traffic, which is false. a local copy of the root simply diffuses
	the traffic.

	the down sides to local copies of the root as seen from the 
	peanut gallery:

	) coherence of the avowed single namespace.  There have been
	  a few threads over the past decade on "bit rot" in the root-hints
	  data.  Local copies of the root zone will have the same bit-rot
	  characteristics
	) the IANA sanctioning alternate roots/namespaces ... "let a 
	  thousand roots bloom..." 
	) just how is the poor application/end user supposed to know 
	  or discriminate some local, walled garden root varient from
	  the one true ICANN root varient?

	but you, no doubt, see a much clearer picture.  please convince
	me that my doubts are groundless... that bit-rot won't happen,
	that the avowed single namespace will remain intact, and that
	there will be trival ways for end users to discover the root of
	the namespace they are using...   if the recommendation to run
	your own copy of the root is approved.

--bill
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop