IETF Logo Mail Archive

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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 15 November 2010 22:34 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 548C13A6D5E for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 14:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.392
X-Spam-Level: *
X-Spam-Status: No, score=1.392 tagged_above=-999 required=5 tests=[AWL=-0.478, 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 RjGsFEd74fEd for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 14:34:36 -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 420823A6D5B for <dnsop@ietf.org>; Mon, 15 Nov 2010 14:34:35 -0800 (PST)
Received: (qmail 93153 invoked from network); 15 Nov 2010 23:08:27 -0000
Received: from softbank219001188004.bbtec.net (HELO ?192.168.1.21?) (219.1.188.4) by necom830.hpcl.titech.ac.jp with SMTP; 15 Nov 2010 23:08:27 -0000
Message-ID: <4CE1B54E.4080106@necom830.hpcl.titech.ac.jp>
Date: Tue, 16 Nov 2010 07:33:50 +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: patrik@frobbit.se
References: <B35360B6-0DB9-49CB-B68E-09DFFFB1ACA0@icann.org> <31FCAB67-9E3E-4E2B-957F-1A1F628AA8FB@hopcount.ca> <4CDC6D23.6070309@necom830.hpcl.titech.ac.jp> <61252B4A-571B-4879-B945-556C03DE2A96@frobbit.se> <4CDDD642.8080108@necom830.hpcl.titech.ac.jp> <FB73AEDC-2B5E-48F9-BCA5-2637CAF6B6A4@frobbit.se> <4CDE6D2D.40805@necom830.hpcl.titech.ac.jp> <4819246C-FF1F-456D-9732-51510F0537A1@frobbit.se> <4CE0F829.1010605@necom830.hpcl.titech.ac.jp> <7F03C666-16F8-49E4-BC56-F5DD441DD970@frobbit.se>
In-Reply-To: <7F03C666-16F8-49E4-BC56-F5DD441DD970@frobbit.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: Mon, 15 Nov 2010 22:34:37 -0000

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?

Though, in general, it may be implied by TLDs, there is no
locale information for TLDs.

Should we extend TLD format to include locale information
for (extended) case insensitivity with a case insensitivity
description language?

						Masataka Ohta

v2.23.0 | Report a Bug | By Email