Re: [dnsext] draft-yao-dnsext-identical-resolution-02 comment

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 14 February 2011 23:49 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8A893A6D7C; Mon, 14 Feb 2011 15:49:37 -0800 (PST)
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A12F3A6DA0 for <dnsext@core3.amsl.com>; Mon, 14 Feb 2011 15:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.257
X-Spam-Level:
X-Spam-Status: No, score=-0.257 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SARE_HTML_URI_LHOST31=1.666]
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 wC-4XRwT86D1 for <dnsext@core3.amsl.com>; Mon, 14 Feb 2011 15:49:35 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id D70813A6D7C for <dnsext@ietf.org>; Mon, 14 Feb 2011 15:49:33 -0800 (PST)
Received: (qmail 84909 invoked from network); 14 Feb 2011 23:59:26 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 14 Feb 2011 23:59:26 -0000
Message-ID: <4D59BF48.3080705@necom830.hpcl.titech.ac.jp>
Date: Tue, 15 Feb 2011 08:48:24 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dnsext@ietf.org
References: <4D48617E.1020408@ogud.com> <3A5CD55E5CCE43F0BA44AAC89BADB866@ics.forth.gr> <20110211020125.GA147@bikeshed.isc.org> <F5CC3C0B5F464E63A4154F62B9BFFDD1@ics.forth.gr>
In-Reply-To: <F5CC3C0B5F464E63A4154F62B9BFFDD1@ics.forth.gr>
Subject: Re: [dnsext] draft-yao-dnsext-identical-resolution-02 comment
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

Vaggelis Segredakis wrote:

> As the Greek registry, offering registrations in Greek characters presented
> the problem with the accent mark "tonos" which is used in the majority of
> Greek words. In capital letters however, the same words are spelled without
> the tonos.

The problem already occurs in ISO 8859/1 with 'y' with diaeresis,
upper case of which is plain 'Y' without diaeresis.

> Their representation in the Punycode is unfortunately different
> and we had to match these up (make similar) for the user,

Definitions, such as case correspondence, in Unicode are not definitions
useful in the real world, which means Unicode is
useless.

> We used the DNAME mechanism with not very satisfactory results.

Suppose you have a label:

	YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY.com

You can match it with:

	YyYYYyYYYYYYyYYYYyYYYYyYYYyYYyYYYyYYYYYyYYyYYyYyYY.com
easily because case correspondence is recognized by DNS protocol.

But, if you want to do the same thing with 'y' with diaeresis,
you can't do it with predefined BNAME/CNAME/DNAME, because of
exponentially many aliases.

However, dynamic generation of *NAME causes performance problem
with secure DNS.

So, you should give up localized DNS, secure DNS or have common
definition on extended case insensitivity (not really defined
in Unicode) between DNS servers and (security aware) clients.

My recommendation is to give up both.

> This way we cannot have consistent mappings since we do not know
> what the programmer has chosen to do with the upper case
> characters, especially in regards to tonos and final sigma.

For precise definitions of extended case insensitivity, we need
a formal language for extended case insensitivity description.

Locale dependent case insensitivity for localized domain names
requires locale information somehow supplied through DNS.

						Masataka Ohta
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext