Re: [DNSOP] draft-yao-dnsop-idntld-implementation-01.txt

Andrew Sullivan <ajs@shinkuro.com> Fri, 06 November 2009 19:33 UTC

Return-Path: <ajs@shinkuro.com>
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 2583F3A69C8 for <dnsop@core3.amsl.com>; Fri, 6 Nov 2009 11:33:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[AWL=0.519, 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 SRs8HMbj15ML for <dnsop@core3.amsl.com>; Fri, 6 Nov 2009 11:33:02 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 1E9463A68E0 for <dnsop@ietf.org>; Fri, 6 Nov 2009 11:33:02 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4DE862FE8CDC for <dnsop@ietf.org>; Fri, 6 Nov 2009 19:33:25 +0000 (UTC)
Date: Fri, 06 Nov 2009 14:33:23 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsop@ietf.org
Message-ID: <20091106193323.GZ17456@shinkuro.com>
References: <20091105205921.GL17456@shinkuro.com> <8F5D82447C5F8BC6B50CD983@Ximines.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8F5D82447C5F8BC6B50CD983@Ximines.local>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [DNSOP] draft-yao-dnsop-idntld-implementation-01.txt
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, 06 Nov 2009 19:33:03 -0000

On Fri, Nov 06, 2009 at 07:06:38PM +0000, Alex Bligh wrote:

> I should probably declare my hand in that I think in most cases the
> variant stuff is a non-problem (blocking is adequate apart from
> where the user is likely to mistype themselves)

According to some people I'm inclined to believe (I can't say this
from personal experience), in non-alphabetic scripts there is indeed a
serious problem with respect to variants.  It's not actually like the
case of (say) colour vs. color, because users tend to have access to
one version or another of the "same" character, but that character is
actually encoded under Unicode as a different character.  This is, I
am led to believe, a very common problem in areas where, for instance,
Simplified and Traditional Chinese characters are both in regular use.
The upshot is that every competent user of the language will recognize
two different arrangements of symbols as "the same word", each user
will be able to type one or the other of the arrangements (but not
both) at their keyboard, and yet the two different arrangements do not
constitute equvalent labels.  So, it's as though by configuring your
system with locale en-CA, you were _unable_ to type "color.com" into a
resolution context.  There is a genuine user problem here (though
whether one should actually solve it is still an open question).

Best,

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.