IETF Logo Mail Archive

Re: [DNSOP] AS112 for TLDs

Florian Weimer <fw@deneb.enyo.de> Sun, 06 April 2008 12:46 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 ADC7A3A6937; Sun, 6 Apr 2008 05:46:42 -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 BEF9C3A687A for <dnsop@core3.amsl.com>; Sun, 6 Apr 2008 05:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 2WoIgYbq3Kgn for <dnsop@core3.amsl.com>; Sun, 6 Apr 2008 05:46:41 -0700 (PDT)
Received: from mail.enyo.de (mail.enyo.de [212.9.189.167]) by core3.amsl.com (Postfix) with ESMTP id E0E083A6937 for <dnsop@ietf.org>; Sun, 6 Apr 2008 05:46:40 -0700 (PDT)
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1JiUDf-0005oB-3G; Sun, 06 Apr 2008 14:43:35 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from <fw@deneb.enyo.de>) id 1JiUDe-0001Od-HD; Sun, 06 Apr 2008 14:43:34 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Mark Andrews <Mark_Andrews@isc.org>
References: <200804032205.m33M5P0W050872@drugs.dv.isc.org>
Date: Sun, 06 Apr 2008 14:43:34 +0200
In-Reply-To: <200804032205.m33M5P0W050872@drugs.dv.isc.org> (Mark Andrews's message of "Fri, 04 Apr 2008 09:05:25 +1100")
Message-ID: <87ve2vxifd.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Cc: dnsop@ietf.org, Edward Lewis <Ed.Lewis@neustar.biz>
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

* Mark Andrews:

> 	There really is only one solution to preventing "bogus"
> 	traffic reaching the root servers and that is to run a local
> 	copy of the root zone.

Or sign the root and use aggressive negative caching (which is currently
prohibited by the RFCs, I'm told).

I agree that information leakage is a problem.  Curiously enough, no
root server or TLD operators that I know of has published some sort of
privacy statement that underlines how they deal with this issue.  It's
also the reason why I think that AS112 for TLDs will not fly.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email