![]() |
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
When ICANN will finally find they're left arm and test its functioning...as we read today Mr. Twomey suggested "puny codes will not be necessary and a true multi-cultural Internet DNS will emerge"
Drewbert wrote he expects current punycode holders would be grandfathered the current domains owned into the new unicode based domains. Does anyone have an example of anything similar happening previously? i understand we cant find an exact example..but anything in the area at all? The only similar case i can see is the limited idn.ru distribution years ago where at some point it has been cancelled and domains revoked due to (i think) Russian government decision? Surely, i don't see this as an option as this time around it is way too many people that invested in idn domains and some are holding them for several years and are operating sites with those names. |
|
|||
|
Quote:
Native users aren't going to be typing punycode urls. They already are typing in UNICODE. Punycode aspect don't have much use to natives |
|
|||
|
Quote:
|
|
|||
|
Quote:
![]() |
|
|||
|
This isn't about "typing stuff in" it's about ownership of domains.
At the moment "英语.com" does not technically exist in the domain name system. It doesn't even resolve in DNS. xn--ghq880n.com exists and using punycode maps to "英语.com" at the client level in the browser, and at the server level at the server. Between those two points, where DNS is used to figure out where queries for "英语.com" should go to, there is NO recognition of "英语.com". Twomey is talking about upgrading the DNS system so that DNS servers recognise "英语.com" (unicode compatible DNS) thus doing away with the need to use punycode at all. This is a major MAJOR undertaking (which is why punycode was decided on) and the longer they take to actually decide to do it, the harder it will be. The question for us is, if/when they do upgrade DNS worldwide so that it recognised unicode natively, will they granfather people's current punycode domains to their unicode equivalents. I think it's up to the registries to decide, and I'm betting they'll decide YES, because it's a 1-to-1 match and if they decide no, they won't be well liked.
__________________
Blame Edwin. |
|
|||
|
Quote:
Little old you and me have little say in the matter. But if they mess about with this for a couple of years, and a few large corporates establish brands behind the domains, then it's no longer just little old you and me, its a shit-load of law suits from companies armed with fleets of lawyers.
__________________
Theres a storm coming...
|
|
||||
|
That's not quite true. Domains are intellectual Property Rights and it is clear that have the rights over the Unicode which you have registered. The fact that there are proposed changes to the encodement system, which frankly aren't ever going to happen, does mean that you legal rights are in anyway negated.
Lets face it. It has taken ICANN 5 years not to be able to cross alias Unicode Ext, with existing TLDs. Even doing this they are shitting themselves. To have a fully native Unicode Root would require the system to be rebuilt from the bottom up. It would with the best will and management systems in the World take at least 10years. Furthermore, it is not at all clear that it would achieve anything useful. Please Mr Twomey deliver on what is required of you is several years overdue, rather than talking semantics about something which you haven't got the first clue on introducing, and for which there is no practical requirement. Implement DNAME and the job is done. If it is beyond you let Verisign sort it out!
__________________
Yours RD. Sales threads older than 30 days are void unless stated otherwise. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|