Re: UTS46 "transitional period"

From: Chris Weber <chris_at_lookout.net>
Date: Tue, 28 Jun 2011 19:41:22 -0700

I was trying to understand the implementation differences in some browsers and registrars.  Using your example from UTS46 http://xn--fa-hia.de/

Opera - error, doesn't resolve
Internet Explorer - error, doesn't resolve
Chrome, FF, and Safari - all resolve with no error

The registrar http://cps-datensysteme.de has this domain name registered and returns its own error page.  I tried registering xn--fa-hia.de at several registrars and received the error that the domain name was invalid, not that it was taken, but that there was an error, or it was illegal punycode.

And why would Chrome, FF, and Safari resolve this - wouldn't the nameprep process under IDNA2003 have it mapped back during the ToAscii or ToUnicode process?

-Chris


On 6/28/2011 5:18 PM, Mark Davis ☕ wrote:

It depends on what you mean.

Registrars could and did allow users to enter in labels for registration that would end up getting remapped to other labels before registration. That is, they could let people enter in faß.de or ÖBB.at, even though what was actually registered as far as the DNS is concerned was fass.de and xn--bb-eka.at (=öbb.at), resp.

What was unfortunate is that apparently not all registrars made it clear to the registrants exactly what was being registered.

They should never have allowed (I don't know whether any did or not) registering punycode that was illegal, like xn--a.

Mark

— Il meglio è l’inimico del bene —

On Tue, Jun 28, 2011 at 14:40, Chris Weber <chris@lookout.net> wrote:

On a tangent, under IDNA2003 rules, shouldn't registration and resolution of the punycode form of "faß.de", which is "xn--fa-hia.de" be illegal since the nameprep process would mapp the eszett to "ss"?

On 6/27/2011 4:14 PM, Mark Davis ☕ wrote:

Once the registries (of that support the 4 special characters) have adopted bundling/blocking policies, then it will be possible for client software to safely move off of the transitional approach. So it is really dependent on the registries' behavior. Different clients may have different thresholds for when to move, depending on their estimation of when enough important registries have  adopted bundling/blocking policies.

>  For example, when all Registries *and* all client software have moved to exclusively support IDNA2008

"All client software" doesn't work, unless you have a coordinate switch date, which people concluded was impractical.

Mark

— Il meglio è l’inimico del bene —

Received on Tue Jun 28 2011 - 21:46:14 CDT