Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
One of the key elements in any domain space is usage. It doesn't matter how potentially "cool" or "interesting" a Top-Level Domain (TLD) is if nobody is actually using it to provide content. It may be overused and totally abused, but "content is king"! The guys in dotMobi posted yesterday about some of the more interesting domains that they had come across recently. What did that lead to? Well I actually got out my phone and browsed the sites to see what all the fuss was about and I was truly impressed.
No that's not really happening, Google is not buying VeriSign. But given Google's ravenous appetite for data, it might find VeriSign quite attractive. VeriSign has both root domain name servers and servers for the .com and .net top level domains (TLDs). VeriSign could data mine the queries coming into those servers and produce a very valuable real-time stream of what users on the net are doing... Google just bought Postini -- and one would have to be fairly naive to believe that Google does not intend to dredge through all...
In one of the first (if not the first) UDRP cases for .cat, the auto giant BMW appears to have filed a WIPO case over the BMW.cat domain name. Other prospective new TLD operators have tried to suggest in ICANN meetings that these new TLDs do not cause problems with cybersquatting or defensive registrations... Obviously, given the above WIPO case, that statement is false.
While travelling home from Geneva, I was thinking quite a lot on the relationship between a ccTLD (registry) and a Country. This is because many countries are starting to talk louder and louder about the responsibilities Countries have on critical infrastructure, or (possibly more important) the management of the critical infrastructure. Will for example any (none?) of ccTLD operators (servers) sustain a denial of service attack of a scale similar to the attack on the root servers? What can ccTLD operators do to resist the malicious attacks? Should this be discussed?
There are a lot of bad, but smart, people out there on the net. They are quick to find and capitalize on vulnerabilities, particularly those vulnerabilities in mass market software. These bad folks are quite creative when it comes to making it hard to locate and shutdown the computers involved. For example, a virus that takes over a victim's computer might communicate with its control point, or send its captured/stolen information, by looking up a domain name. Normally domain names are somewhat static - the addresses they map to don't change very frequently - typically changes occur over periods measured in months or longer.
Today on Dave Farber's IP list, someone revived the ancient argument that ICANN imposes limits on the number of top level domains (TLDs) because to have more than a few will cause DNS to wobble and cause the internet to collapse. Although long discredited, that argument hangs around like a zombie. ICANN has never been able to adduce a shred of proof that there is anything to support that assertion...
With the IGF underway, there's a lot of discussion surrounding Internationalized Domain Names (IDN). There has been lots of great progress in IDN technology with IE7 and Firefox browsers now fully IDN-Aware, strong IDN registrations and websites behind them. Now that many of the hurdles to implementation have been addressed to where the technology is either currently available to most internet users, or shall be soon, we now focus to the other aspects of IDN...
In the last few years there have been many discussions on how the Internet is governed, and how it should be governed. The whole World Summit on the Information Society (WSIS) ended talking about this problem. It caused exchange of letters between the US Secretary of State and the European Union presidency. And it caused a public discussion, organized by the US Department of Commerce on that issue. I saw some reflection of this discussion and here are some comments on that. My colleague Milton Mueller of the Syracuse University sent me an e-mail today in which, among other, it says, "A global email campaign by IGP generated comments from 32 countries...
With all of the recent excitement about *.cm, the Cameroonian wildcard that someone is using to collect vast numbers of mistyped .com addresses, I wondered how many other wildcards there were at the DNS top level. There's a total of 13. Half of the wildcards are harmless. The *.museum wildcard leads to a registry page that helps guess what you might have been looking for. ...The .mp page also claims that .mp is for Mobile Phone rather than for the Marianas Islands, but they're hardly the only small poor island to try to cash in on their ccTLD, and they at least run it themselves.
The .cm (Cameroon) ccTLD operators have discovered that since their TLD is simply one omitted letter away from .com, that there is a gold mine in the typo traffic that comes their way. Accordingly, Cameroon has now wild-carded its ccTLD and is monetizing the traffic. The upshot is that, if the Neiman Marcus / Dotster lawsuit over 27 domain names was properly characterized as "massive", then the Cameroonians are now going well beyond massive...
A World-Renowned Source for Internet Developments. Serving Since 2002.