A couple of draft documents you should look at

[IDNer]

Originally Posted by bramiozo

..however, once the browsers are up to speed with this upcoming IETF it could still be blocked.

The spirit of the internet is World Wild Web -
To block something which is available & alive on the internet
(and they didn't make anything wrong)
is very ridiculous -

[bramiozo]

Blocked by technical specifications is something different then censorship, the site isn't blocked, the domain just doesn't resolve in the browser (eventually).

There's no requirement for browsers to block single character ascii-domains, browsers don't have to perform any actions for ascii-domains (right?).

I say all this under the assumption that the browsers completely implement the idna-protocol and with the assumption that these characters are still disallowed in the following release (since this is only a draft).

[bramiozo]

Originally Posted by Rubber Duck

I think you will find that they will be screwed at the Nameprep level in the browser.

Nothing different will happen in the DNS.

ICANN can of course force registrars to delete disalllowed strings, but this probably won't be necessary as they won't resolve anyway.

No apology necessary!

Unless he buys poundsign.com and let's people download a plug-in to resolve £.com. ..

[bramiozo]

built a compliance checker;IDNtools

will add some ajax stuff later.