Re: [DNSOP] AS112 for TLDs

Florian Weimer <fw@deneb.enyo.de> Sun, 06 April 2008 13:16 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@lists.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 465293A6CA5; Sun, 6 Apr 2008 06:16:07 -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 74D8C3A698C for <dnsop@core3.amsl.com>; Sun, 6 Apr 2008 06:16:02 -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 mY+7oZchCG69 for <dnsop@core3.amsl.com>; Sun, 6 Apr 2008 06:15:59 -0700 (PDT)
Received: from mail.enyo.de (mail.enyo.de [IPv6:2001:14b0:202:1::a7]) by core3.amsl.com (Postfix) with ESMTP id DCC7428C1AC for <dnsop@ietf.org>; Sun, 6 Apr 2008 06:15:41 -0700 (PDT)
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1JiUij-00068G-2a; Sun, 06 Apr 2008 15:15:41 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from <fw@deneb.enyo.de>) id 1JiUii-0001Wy-Di; Sun, 06 Apr 2008 15:15:40 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Joe Baptista <baptista@publicroot.org>
References: <200804032205.m33M5P0W050872@drugs.dv.isc.org> <87ve2vxifd.fsf@mid.deneb.enyo.de> <874c02a20804060605q75cd0db1h696b0772fc6f2ec@mail.gmail.com>
Date: Sun, 06 Apr 2008 15:15:40 +0200
In-Reply-To: <874c02a20804060605q75cd0db1h696b0772fc6f2ec@mail.gmail.com> (Joe Baptista's message of "Sun, 6 Apr 2008 09:05:24 -0400")
Message-ID: <87bq4nxgxv.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Cc: dnsop@ietf.org, Mark Andrews <Mark_Andrews@isc.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

* Joe Baptista:

>> 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.

> They are not the ones generating this traffic.  Its users as they cross over
> dns zones.  i.e. travelers from china staying at a hotel in the USA who
> can't access their language script idn national china tlds via the legacy
> IANA root.

This doesn't exempt them from protecting that traffic (which they
actually do in some form, you can't download it on a public FTP site,
for instance).

>> It's also the reason why I think that AS112 for TLDs will not fly.
>
>
> It will.  Makes the perfect dns equivalent of the bin bucket trash
> can.

It means that everybody who can make a BGP announcement can legitimately
hijack DNS traffic to those TLDs.  Is this really what we want?
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop