Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 22 February 2011 23:37 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 732523A697B; Tue, 22 Feb 2011 15:37:45 -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 39FC63A697B for <dnsext@core3.amsl.com>; Tue, 22 Feb 2011 15:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.097
X-Spam-Level:
X-Spam-Status: No, score=-0.097 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 W5iWKcQljJhY for <dnsext@core3.amsl.com>; Tue, 22 Feb 2011 15:37:43 -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 EF4343A67FA for <dnsext@ietf.org>; Tue, 22 Feb 2011 15:37:42 -0800 (PST)
Received: (qmail 93795 invoked from network); 22 Feb 2011 23:50:13 -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; 22 Feb 2011 23:50:13 -0000
Message-ID: <4D64489B.7020901@necom830.hpcl.titech.ac.jp>
Date: Wed, 23 Feb 2011 08:36:59 +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: <20110216165921.GW96213@shinkuro.com> <3B90ED2E-980D-4B01-889F-447D66D0B58D@insensate.co.uk> <20110216174011.GZ96213@shinkuro.com> <20110218143653.GC84482@bikeshed.isc.org> <20110218151209.GF66684@shinkuro.com> <4D5EEE09.4080405@dougbarton.us> <20110218222950.GL74065@shinkuro.com> <4D5F270F.20401@abenaki.wabanaki.net> <199C7B2B4228461FB024E59A990DB46D@ics.forth.gr> <4D641DB6.4090705@necom830.hpcl.titech.ac.jp> <20110222205617.GS53815@shinkuro.com>
In-Reply-To: <20110222205617.GS53815@shinkuro.com>
Subject: Re: [dnsext] we need help to make names the same, was 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

Andrew Sullivan wrote:

> Moderator hat on.

You shouldn't.

>> Some of the problems can be solved only by fundamental redesign
>> of character encoding (effectively abandoning Unicode).
>>
>> Avoiding to do so, more than 10 years have wasted already.

> Repeating over and over again that it won't work isn't helpful.  If
> you have specific criticisms of a specific proposal, that is helpful,
> and I'll be happy to read it.

Specific proposals on the sameness problem I made this time are:

	to give up to have localized domain name

or

	develop extended case insensitivity description language

and

	to give up DNSSEC or run extended case insensitivity
	database on clients

which you failed to read.

The latter proposal is similar to John Levine's recognition:

> The pattern language for encoding variant names would probably be more
> complex than people would like, but if we are serious that all the
> spellings of Greek words are equivalent, or traditional and simplified
> Chinese are equivalent, I don't see how anything simpler could do the
> job.

Remember possible case insensitivity issues related to Greek or
Chinese equivalent of

	yyyyyyyyYyyyyyYyyyYyyyyyYyyyyyyyyyyyYyyyy

or

	iPod

That you want to have IDN politically does not mean IDN
exist and even localized domain names are so hard to have,
which is the technical reality.

However, you are saying you can't accept the technical
consequences only to waste yet another 10 years.

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