Standardizing on IDNA 2003 in the URL Standard

[Jiankang Yao]

Aà.com has been registered.
http://www.verisigninc.com/en_US/products-and-services/register-domain-names/whois/index.xhtml 

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
   Status: clientTransferProhibited
   Updated Date: 12-sep-2013
   Creation Date: 22-feb-2009
   Expiration Date: 22-feb-2014








Jiankang Yao

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"
> 
> 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.

A

-- 
Andrew Sullivan
ajs at anvilwalrusden.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/idna-update/attachments/20140116/bb3a27f4/attachment-0001.html>