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

James Seng <james@seng.sg> Sat, 07 November 2009 12:10 UTC

Return-Path: <james.seng@gmail.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 67FCE3A689E for <dnsop@core3.amsl.com>; Sat, 7 Nov 2009 04:10:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 u8BmiYQP7LqL for <dnsop@core3.amsl.com>; Sat, 7 Nov 2009 04:10:01 -0800 (PST)
Received: from mail-iw0-f202.google.com (mail-iw0-f202.google.com [209.85.223.202]) by core3.amsl.com (Postfix) with ESMTP id 1CAF13A67FC for <dnsop@ietf.org>; Sat, 7 Nov 2009 04:10:01 -0800 (PST)
Received: by iwn40 with SMTP id 40so1477794iwn.32 for <dnsop@ietf.org>; Sat, 07 Nov 2009 04:10:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=awuRVDwoFJ/ih0H4vdPKXxSGB+p/O7zqPoNLf+3Unr4=; b=gFthgRDyVj9jHVuC+YXVuYc/EWETS0Q7/leKdUv05XqOUqJ4NoDn2OV7hMr1f2Wrpn 8WWAavSprE4L+qLNM2lpfb4tNNPpSnWClYjGb6mRWfEcBnp4r/CPHJn4LUPkCp+du22f ohJxCxWxysUFvZMlWfpokDBTBCIbzNN8IjyXA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=T/Z62aDbuEEJPIQo6WWbQJOD37zrGCtNnmaRRK8YPPiyClnCV0CdsFhNk+q9NT236U MfHI/zbAXFtS28GClusAckXlPZ8c3Jd8FkC6AaQ+e92qU70OymPGWMJlzgMeEQk2I+Gn 9jxLA2aPy34XZJNyMPZxcsa8OHw/qRnftS13M=
MIME-Version: 1.0
Sender: james.seng@gmail.com
Received: by 10.231.9.218 with SMTP id m26mr1183030ibm.29.1257595822102; Sat, 07 Nov 2009 04:10:22 -0800 (PST)
In-Reply-To: <20091106193323.GZ17456@shinkuro.com>
References: <20091105205921.GL17456@shinkuro.com> <8F5D82447C5F8BC6B50CD983@Ximines.local> <20091106193323.GZ17456@shinkuro.com>
From: James Seng <james@seng.sg>
Date: Sat, 07 Nov 2009 20:10:02 +0800
X-Google-Sender-Auth: de53642af55dfb1c
Message-ID: <558a39a60911070410p54bd1810n44ea845d2698b866@mail.gmail.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Content-Type: multipart/alternative; boundary="0003255735d23f5a270477c6d8d9"
Cc: dnsop@ietf.org
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: Sat, 07 Nov 2009 12:10:02 -0000

"There is a genuine user problem here (though whether one should actually
solve it is still an open question)."

It is a genuine user problem but I disagree with your latter statement.

It is not an open question it must be solved. It is a serious enough problem
for Chinese that it must be resolve for the Chinese user. The open question
is "how", not "if".

For some background on CJK ideograph, you may refer to an expired draft I
wrote many years ago

http://james.seng.sg/files/draft-ietf-idn-cjk-01.pdf

RFC 3743 will also be a good point of reference.

-James Seng

On Sat, Nov 7, 2009 at 3:33 AM, Andrew Sullivan <ajs@shinkuro.com> wrote:

> 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.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>