Re: [DNSOP] draft-liman-tld-names-04

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 26 November 2010 23:14 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 9AEFE28C127 for <dnsop@core3.amsl.com>; Fri, 26 Nov 2010 15:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.87
X-Spam-Level: *
X-Spam-Status: No, score=1.87 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 krKEsASKreyk for <dnsop@core3.amsl.com>; Fri, 26 Nov 2010 15:14:57 -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 6A8163A69BF for <dnsop@ietf.org>; Fri, 26 Nov 2010 15:14:57 -0800 (PST)
Received: (qmail 66847 invoked from network); 26 Nov 2010 23:52:30 -0000
Received: from ntymns019164.ymns.nt.ngn.ppp.infoweb.ne.jp (HELO ?192.168.1.6?) (175.179.228.164) by necom830.hpcl.titech.ac.jp with SMTP; 26 Nov 2010 23:52:30 -0000
Message-ID: <4CF03F6C.7000405@necom830.hpcl.titech.ac.jp>
Date: Sat, 27 Nov 2010 08:14:52 +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.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20101117091928.GA30093@nic.fr> <4CE9E942.20906@dougbarton.us> <0E561274-43FE-4657-951E-74C8FF0FD307@hopcount.ca> <4CEC43DC.1060709@dougbarton.us> <E7796748-6880-4928-B96D-0024E27E98D5@hopcount.ca> <4CEC69C5.3040209@dougbarton.us> <7B9EF625-1E25-42BE-9546-61C5B7EFC6DA@hopcount.ca> <8CEF048B9EC83748B1517DC64EA130FB43E0037FD1@off-win2003-01.ausregistrygroup.local> <20101124142303.GB19441@shinkuro.com> <alpine.LSU.2.00.1011251734170.4075@hermes-2.csi.cam.ac.uk> <20101125175247.GH21047@shinkuro.com> <alpine.LSU.2.00.1011261558520.4075@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1011261558520.4075@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] draft-liman-tld-names-04
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, 26 Nov 2010 23:14:58 -0000

Tony Finch wrote:

> It describes the current
> No distinction is made between upper and lower case.

How can you define upper case of 'y' with diaeresis' in Dutch
context where

   http://en.wikipedia.org/wiki/IJ_%28digraph%29
   (lowercase y with diaeresis), ij and Y, IJ are identical.

?

Note that upper case of 'y' with diaeresis' is not 'Y' with
diaeresis but plain 'Y' without diaeresis, because, unlike 'i'
and 'j', 'I' and 'J' do not have a dot in their character
shapes.

> In order to accommodate the wish to express TLD names in scripts
> other than the ASCII subset of Latin, it is necessary to allow
> non-alphabetic characters in the corresponding TLD DNS-Labels.

The example above is using only alphabetic Latin characters.

> Following past practice, the U-label form of a TLD name is
> restricted by applying rules analogous to those already
> imposed on ASCII TLD DNS-Labels.

So, how can you define upper case of 'y' with diaeresis' in
Dutch context?

And, beyond Latin, how can you define similar equivalence,
which is necessary for TLD registration operation, of extended
case insensitivities?

						Masataka Ohta