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> Wed, 16 February 2011 08:05 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 808A03A6B6B for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 00:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.132
X-Spam-Level:
X-Spam-Status: No, score=-0.132 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 G4iR-E95BhjL for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 00:05:18 -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 7738C3A68A3 for <dnsext@ietf.org>; Wed, 16 Feb 2011 00:05:18 -0800 (PST)
Received: (qmail 36237 invoked from network); 16 Feb 2011 08:15:51 -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; 16 Feb 2011 08:15:51 -0000
Message-ID: <4D5B8529.8030509@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 17:04:57 +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: John Levine <johnl@iecc.com>
References: <20110216073338.7251.qmail@joyce.lan>
In-Reply-To: <20110216073338.7251.qmail@joyce.lan>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: dnsext@ietf.org
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>
X-List-Received-Date: Wed, 16 Feb 2011 08:05:19 -0000

John Levine wrote:

> 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.

I'm happy that you seems to have reached the same conclusion
as mine:

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

But, then, the issue is purely about character encoding which
is better handled by clients outside of DNS.

Note that people working on secure DNS (I'm not) won't welcome
proposals to support yet another type of wild card.

Or, if you think pattern should be locale dependent, I agree
that its support must involve DNS protocol. Locale information
must be supplied from DNS, at least.

						Masataka Ohta