W3C home > Mailing lists > Public > uri@w3.org > January 2014

Re: Re: Standardizing on IDNA 2003 in the URL Standard

From: Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Wed, 15 Jan 2014 21:52:27 -0500
To: Jiankang Yao <yaojk@cnnic.cn>
Cc: Anne van Kesteren <annevk@annevk.nl>, Mark Davis ? <mark@macchiato.com>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, John C Klensin <klensin@jck.com>, IDNA update work <idna-update@alvestrand.no>, Vint Cerf <vint@google.com>, "www-tag.w3.org" <www-tag@w3.org>
Message-ID: <20140116025226.GJ22105@mx1.yitter.info>
On Thu, Jan 16, 2014 at 10:07:36AM +0800, Jiankang Yao wrote:
>   In which section of rfc idnabis does say some meaning related to  that " "Aà.com" is not PVALID"?

Upper case characters are not PVALID.  This is because of B:
toNFKC(toCaseFold(toNFKC(cp))) != cp.  In appendix B.1 it's
illustrated in this entry:

> I check Aà.com in verisign conversion tool, it shows "xn--a-sfa.com"
> http://mct.verisign-grs.com/convertServlet?input=A%C3%A0.com 
> does it follow idna2003 instead of idnabis?

I have no idea.  Maybe it has a bug.  Or maybe it does case mapping
before it touches the string; that's what RFC 5895 suggests.  In that
case, of course, the Verisign conversion tool includes some things
that applications are supposed to do.


Andrew Sullivan
Received on Thursday, 16 January 2014 02:53:00 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 10 October 2021 22:17:57 UTC