Re: [DNSOP] new draft about idn tld variants implementation
Alfred Hönes <ah@TR-Sys.de> Fri, 16 October 2009 14:49 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
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 E05543A6853 for <dnsop@core3.amsl.com>; Fri, 16 Oct 2009 07:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.389
X-Spam-Level: **
X-Spam-Status: No, score=2.389 tagged_above=-999 required=5 tests=[AWL=1.138, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 8Vago6r-UzUw for <dnsop@core3.amsl.com>; Fri, 16 Oct 2009 07:49:37 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id EAD6C3A67B2 for <dnsop@ietf.org>; Fri, 16 Oct 2009 07:49:35 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA244024534; Fri, 16 Oct 2009 16:48:55 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id QAA00596; Fri, 16 Oct 2009 16:48:53 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <200910161448.QAA00596@TR-Sys.de>
To: dnsop@ietf.org
Date: Fri, 16 Oct 2009 16:48:53 +0200
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
Subject: Re: [DNSOP] new draft about idn tld variants implementation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 16 Oct 2009 14:49:38 -0000
Another point: The draft is speaking abut "DNAME _in_ the root". According to my surficial knowledge, DNAME RRs 'live' at the _apex_ of the zone that shall be redirected, not at the delegation point -- or did I miss something? Within each zone, there may be at most one DNAME RR, and if so, it must be at the apex of the zone. So if you have a variant TLD, this variant would need to be delegated from the root zone (via NS RRs as usual) anyway, and the owner / DNS operator of the delegated variant TLD (ICANN should perhaps ensure that's the same one as for the 'original' TLD!) simply publishes a tiny zone with the DNAME RR. >From the point of view of the root zone, there's no difference in the 'look and feel' of an 'original' TLD and a variant TLD. Most likely however, the name servers for the variants would be the same as for the basic TLD. But the owner / DNS operator of the 'original' TLD and its variants is entirely free to manage the equivalence of these domains in any feasable way, one of it being DNAME; however, if they have server software that can perform the aliasing 'on the fly' from a database, they could use that. It is a contractual matter between ICANN and the TLD owner to ensure that the equivalence is maintained under all circumstances, not a DNS protocol issue. Or is it the intent to have the variant TLS zones all be served by the root servers as well, to which you oppose ? I've not heard about such proposal, but admittedly I did not care much about such questions in the past. If ICANN would decide to have the DNAME-based variant TLD zones (those tiny zones with only the SOA, the DNAME, and maybe a few other RRs) be served within the root server organization, they would not necessarily have to do that with the original root servers; they also could deploy additional servers for this purpose and delegate the variant TLDs to these servers. Even if the variant zones were to be served by the original root servers, there would have to be delegations (to the same servers) via NS RRs, insn't it? Kind regards, Alfred Hönes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+
- Re: [DNSOP] new draft about idn tld variants impl… Andrew Sullivan
- Re: [DNSOP] new draft about idn tld variants impl… Ray.Bellis
- [DNSOP] new draft about idn tld variants implemen… Yao Jiankang
- Re: [DNSOP] new draft about idn tld variants impl… Mark Andrews
- Re: [DNSOP] new draft about idn tld variants impl… YAO Jiankang
- Re: [DNSOP] new draft about idn tld variants impl… Sebastian Castro
- Re: [DNSOP] new draft about idn tld variants impl… Mark Andrews
- Re: [DNSOP] new draft about idn tld variants impl… Alfred Hönes
- Re: [DNSOP] new draft about idn tld variants impl… Niall O'Reilly
- Re: [DNSOP] new draft about idn tld variants impl… Chris Thompson
- Re: [DNSOP] new draft about idn tld variants impl… Andrew Sullivan
- Re: [DNSOP] new draft about idn tld variants impl… Alfred Hönes
- Re: [DNSOP] new draft about idn tld variants impl… Chris Thompson
- Re: [DNSOP] new draft about idn tld variants impl… joao damas
- Re: [DNSOP] new draft about idn tld variants impl… YAO Jiankang
- Re: [DNSOP] new draft about idn tld variants impl… Paul Hoffman
- Re: [DNSOP] new draft about idn tld variants impl… YAO Jiankang