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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 16 November 2010 00:23 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 B20AF28C185 for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 16:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.488
X-Spam-Level: *
X-Spam-Status: No, score=1.488 tagged_above=-999 required=5 tests=[AWL=-0.382, 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 altLA00N61au for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 16:23:19 -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 367B428C1DD for <dnsop@ietf.org>; Mon, 15 Nov 2010 16:23:11 -0800 (PST)
Received: (qmail 95552 invoked from network); 16 Nov 2010 00:57:27 -0000
Received: from softbank219001188004.bbtec.net (HELO ?192.168.1.21?) (219.1.188.4) by necom830.hpcl.titech.ac.jp with SMTP; 16 Nov 2010 00:57:27 -0000
Message-ID: <4CE1CED4.4020008@necom830.hpcl.titech.ac.jp>
Date: Tue, 16 Nov 2010 09:22:44 +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: "]ke Nordin" <moose@netia.se>
References: <B35360B6-0DB9-49CB-B68E-09DFFFB1ACA0@icann.org> <7F03C666-16F8-49E4-BC56-F5DD441DD970@frobbit.se> <4CE1B54E.4080106@necom830.hpcl.titech.ac.jp> <201011152351.28925.moose@netia.se>
In-Reply-To: <201011152351.28925.moose@netia.se>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org
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: Tue, 16 Nov 2010 00:23:20 -0000

]ke Nordin wrote:

>> Some non-ASCII name wrote:
>>> No, that statement is not correct. The mapping you might want
>>> depends on context, and that not only because of language,
>>> but also where the language is used. I.e. it depends on what
>>> locale you are using.

>> How the locale information could be supplied?

> I think that is rather far out of scope for the document in question.

Then, how the locale information for TLDs could be supplied?

> If every single standards document must address _every_  potential
> issue, the density of IETF work would have a significant Schwarzschild

I'm not saying that the document should specify a case
insensitivity description language nor that IETF should
specify the language.

But, there should be a field in TLD names to store the locale
information.

						Masataka Ohta