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

Alex Bligh <alex@alex.org.uk> Wed, 16 February 2011 07:43 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 6E5733A6DD7; Tue, 15 Feb 2011 23:43:08 -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 923FF3A6DD4 for <dnsext@core3.amsl.com>; Tue, 15 Feb 2011 23:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ylNtc7iFBZNX for <dnsext@core3.amsl.com>; Tue, 15 Feb 2011 23:43:05 -0800 (PST)
Received: from mail.avalus.com (mail.avalus.com [89.16.176.221]) by core3.amsl.com (Postfix) with ESMTP id 735843A6DD9 for <dnsext@ietf.org>; Tue, 15 Feb 2011 23:43:05 -0800 (PST)
Received: from [10.93.101.159] (87-194-71-186.bethere.co.uk [87.194.71.186]) by mail.avalus.com (Postfix) with ESMTPSA id 5A7DBC5641A; Wed, 16 Feb 2011 07:43:31 +0000 (GMT)
Date: Wed, 16 Feb 2011 07:43:30 +0000
From: Alex Bligh <alex@alex.org.uk>
To: John Levine <johnl@iecc.com>, dnsext@ietf.org
Message-ID: <BE5119E0A9AF9C470D3D362A@nimrod.local>
In-Reply-To: <20110216073338.7251.qmail@joyce.lan>
References: <20110216073338.7251.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Disposition: inline
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
Reply-To: Alex Bligh <alex@alex.org.uk>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

--On 16 February 2011 07:33:38 +0000 John Levine <johnl@iecc.com> 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.

The fact that 2 or more spellings (*) are equivalent does not necessarily
mean both always need to give the same DNS results; indeed as much
trailed previously, this may be undesirable. I still think this is the
wrong "job" to do, so the fact this is might be simplest way of doing
something undesirable is not really a positive. However, except in
the cases of combinatorial explosion, manual provisioning would seem
to be far simpler.

(*) I think it's really about orthographic representation rather than
spelling: we aren't really talking about jail.com and gaol.com, are
we?

-- 
Alex Bligh
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext