Re: Update of RFC 2606 based on the recent ICANN changes ?

John Levine <johnl@iecc.com> Mon, 07 July 2008 17:19 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DC9B3A690A; Mon, 7 Jul 2008 10:19:22 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB8613A690A for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 10:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.669
X-Spam-Level:
X-Spam-Status: No, score=-9.669 tagged_above=-999 required=5 tests=[AWL=-1.385, BAYES_00=-2.599, MANGLED_SEX=2.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
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 cR6i0ioVMGnj for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 10:19:21 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 9F48C3A68D7 for <ietf@ietf.org>; Mon, 7 Jul 2008 10:19:20 -0700 (PDT)
Received: (qmail 84578 invoked from network); 7 Jul 2008 17:19:26 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 7 Jul 2008 17:19:26 -0000
Date: 7 Jul 2008 17:19:26 -0000
Message-ID: <20080707171926.28210.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <48724347.6020500@dcrocker.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>What will be the impact of having, perhaps,
>
>   1)  millions of entries in the root servers, and

Let's start by considering thousands of entries, since I see little
reason to expect even that many from ICANN's current plans.

>   2)  constant traffic banging on those servers?

The latest CAIDA study says:

* The overall query traffic experienced by the roots continues to
  grow. The observed 2007 query rate and client rate was 1.5-3X above
  their observed values in 2006

* The proportion of invalid traffic, i.e., DNS pollution, hitting the
  roots is still high, over 99% of the queries should not even be sent
  to the root servers. We found an extremely strong correlation both
  years: the higher the query rate of a client, the lower the fraction
  of valid queries.

That suggests that if the legit traffic increased by an order of
magnitude, it would still be down in the noise compared to the junk.
Conversely, if root server traffic is an issue, getting networks to
clean up their DNS traffic would be much more effective than limiting
the number of TLDs.

http://www.caida.org/research/dns/roottraffic/comparison06_07.xml

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf