RE: DNS and URI persistence using IDN

The good (sic) news is: URIs don't allow non-ASCII characters in any form (%-hex encoded or not) in the host portion, so this *isn't* in the category of DNS and URI persistence. 

Rather, it's in the category of "resources you'd like to be able to create an (internationalized) uniform resource identifier for.

The handling of internationalized domain names in IRIs is one of the areas still open for review and consensus in the IRI draft.  The previous IRI proposed standard doesn't match implementations.   Whether the proposed spec matches implementations is unclear. It is dismaying that there has been scant attention to the IRI document from IRI implementors (in what seems to me to be a kind of self-fulfilling prediction ).

The bad news is that without more attention from actual IRI implementors, progress will continue to stall.

Larry
--
http://larry.masinter.net



-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Karl Dubost
Sent: Wednesday, March 16, 2011 1:54 PM
To: www-tag@w3.org List
Subject: DNS and URI persistence using IDN

Yet another story in the category of DNS and URI persistence.

In this case, it will have an impact on a few people but probably not at large scale.  The RFC 5892[1] forbids some domain name types such as the character "⁂" U+2042 in a domain name. Someone [2] has received an email from his registrar to inform him that the domain name would disappear. The calendar of when is not yet sure. 


[1]: http://www.rfc-editor.org/rfc/rfc5892.txt

[2]: http://www.madore.org/~david/weblog/#d.2011-03-10.1857 (French)
 
-- 
Karl Dubost - http://dev.opera.com/

Developer Relations & Tools, Opera Software

Received on Thursday, 17 March 2011 14:20:43 UTC