Re: [DNSOP] AS112 for TLDs

Mark Andrews <Mark_Andrews@isc.org> Mon, 03 December 2007 21:36 UTC

Return-path: <dnsop-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzIxZ-0001vJ-Dm; Mon, 03 Dec 2007 16:36:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzIxZ-0001vB-1e for dnsop@ietf.org; Mon, 03 Dec 2007 16:36:13 -0500
Received: from [2001:df8:0:64:216:6fff:fe46:b75d] (helo=drugs.dv.isc.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzIxW-0005vO-Kn for dnsop@ietf.org; Mon, 03 Dec 2007 16:36:13 -0500
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id lB3La6Mu001901; Tue, 4 Dec 2007 08:36:07 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200712032136.lB3La6Mu001901@drugs.dv.isc.org>
To: Phil Regnauld <regnauld@catpipe.net>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: [DNSOP] AS112 for TLDs
In-reply-to: Your message of "Mon, 03 Dec 2007 20:52:32 BST." <20071203195232.GA4461@catpipe.net>
Date: Tue, 04 Dec 2007 08:36:06 +1100
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: dnsop@ietf.org
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Errors-To: dnsop-bounces@ietf.org

> William F. Maton Sotomayor (wmaton) writes:
> > 
> >  I think it very may well be suited to that task, but are we crossing a lin
> e 
> >  here that may result down a path we might regret later on.  I think what 
> >  would need to be worked out is what criteria would be used to declare a 
> >  local or nonsense domain, nonsense or junk, and have that suitably delegat
> ed 
> >  to AS112.  It could go ad infinitum (ever word in every language), or it 
> >  could be we need to take whatever floats to the top 25 of a domain lookup 
> >  chart.  Of course, someone needs to determine what makes a good sample to 
> >  create that statistic.
> 
> 	The first step is to decide whether delegating to AS112 is reserved
> 	to standardized (read: RFC) zones, like RFC1918, 169.254, etc..., or
> 	whether anything sufficiently large -- and bogus -- is sufficient.
> 
> 	.local fits the latter criteria.  But yes, it does make the requirement
> 	criteria more fuzzy.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www1.ietf.org/mailman/listinfo/dnsop

	We should be looking at mechanisms to allow the root zone to
	be distributed to every iterative resolver in the world.

	You then don't have to use AS112 to absorb the load.  The local
	resolver will answer the query.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www1.ietf.org/mailman/listinfo/dnsop