Standardizing on IDNA 2003 in the URL Standard
yaojk at cnnic.cn
Thu Jan 16 04:03:18 CET 2014
Aà.com has been registered.
Your search for Aà.com returns the below results:
Whois Server Version 2.0
Domain Name: AÀ.COM (XN--A-SFA.COM)
Registrar: INTERNET.BS CORP.
Whois Server: whois.internet.bs
Referral URL: http://www.internet.bs
Name Server: NS1.SEDOPARKING.COM
Name Server: NS2.SEDOPARKING.COM
Updated Date: 12-sep-2013
Creation Date: 22-feb-2009
Expiration Date: 22-feb-2014
From: Andrew Sullivan
Date: 2014-01-16 10:52
To: Jiankang Yao
CC: Anne van Kesteren; Mark Davis ?; PUBLIC-IRI at W3.ORG; uri at w3.org; John C Klensin; IDNA update work; Vint Cerf; www-tag.w3.org
Subject: Re: Re: Standardizing on IDNA 2003 in the URL Standard
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:
003A..0060 ; DISALLOWED # COLON..GRAVE ACCENT
> I check Aà.com in verisign conversion tool, it shows "xn--a-sfa.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.
ajs at anvilwalrusden.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update