Posts Tagged VeriSign

What the Heck is ICANN Doing with Domain Names?

Last week stories broke about a significant change in the way Internet addressing will be managed. The Internet Corporation for Assigned Names and Numbers (ICANN) has opened up the process of assigning new top level domains (TLD’s), such as .com and .net. Potentially any string of letters could be a TLD — maybe we’ll see www.products.walmart? However there appears to be lots of procedures to iron out before any prospective new TLDs hit the market.

Here’s some coverage:

Ars Technica:

http://arstechnica.com/news.ars/post/20080626-confusion-icann-opens-up-pandoras-box-of-new-tlds.html

NY Times:

http://tinyurl.com/5a35kn

Here’s a very detailed read from John Levine at CircleID:

http://www.circleid.com/posts/86299_icann_new_top_level_domains/

Clearly nothing is going to happen right away, and the devil(s) will be in the details. Plus there are already at last count 162 million registered domain names, so a lot will be required to produce a new TLD that actually makes a difference. Here’s my early list:

  • User adoption — the old chicken and the egg. An organization with a lot of money and influence will have to invest both to change user perceptions of Internet addressing. It’s a steep hill to climb. Combined, .com and .net total around 85 million domains (with .com about 74M of that) and will be the TLD leaders for a long time to come. (Granted both China’s .cn and Germany’s .de are now bigger than .net)
  • You’ll need a solid sales channel. The successful TLD operator will need good connections to the existing base of registars, and a compelling value proposition for registrars to sell the new extension over other, more established ones.
  • Global resolution is a big responsibility. The new extension will have to always work, anywhere on the globe. That means servers and data centers in multiple locations, load balancing, maintenance, etc. etc.
  • Domain names in foreign languages sound very interesting. But as Levine notes these could get hopelessly bogged down in litigation, and many countries particularly in Asia have been forging ahead with their own fully native language solutions while ICANN has dithered over this question for years.

No doubt this will be a very interesting story to follow. If I had to bet my lunch money today, I’d say that the established players in the registry market who already know how to operate and support TLDs will be the main beneficiaries of ICANN’s decision. They’ve made the technology investments and mastered ICANN esoterica. Any newcomer will have to partner with one of them if a new TLD hopes to attract wide spread adoption.

Add comment July 3, 2008

Five Years Later, a SiteFinder Patent?

Saw an interesting news item that broke Monday courtesy of DomainNameNews and SlashDot that hasn’t been broadly covered yet. Apparently VeriSign has been awarded a patent for the resolution of mis-typed domain names. This was at the heart of the controversy back in 2003 around their SiteFinder Service. Amidst a storm of criticism ICANN insisted VeriSign shut down the service, and the company eventually agreed.

Patent: http://www.domainnamenews.com/registries/verisign-receives-sitefinder-patent/1559

SiteFinder: http://www.itworld.com/Man/2681/031006sitefinder/

Personally I believe if VeriSign had been less secretive about its plans and had briefed important Internet constituencies beforehand about this change to how the Internet operated, there would have been less criticism. VeriSign and ICANN eventually settled their differences re SiteFinder, and as part of the re-awarding of the .com franchise VeriSign promised never to bring a SiteFinder-like service back. But, this patent is interesting for what it means in the present, not the past.

Many companies currently resolve incorrect domain names to pages that contain advertising. They don’t do it the way VeriSign did it, by changing the way the root server operates for .com addresses. But the result is the same, and would seem to be covered by the patent. Companies like Earthlink, Verizon and OpenDNS bring their customers to advertising pages every time they “fat-finger” a domain name. Just think about how  often we all do this, and you can imagine the amount of Internet traffic potentially involved. Some of these companies weren’t re-directing this traffic safely — there were security problems with the ad partner Earthlink chose to deal with:

http://www.portfolio.com/news-markets/top-5/2008/04/21/Hackers-Can-Exploit-Error-Page-Ads

So, the government seems to have handed VeriSign a new revenue stream. Letters may be going out shortly demanding a licensing fee — or maybe they’ve already been sent.

UPDATE — AP wrote story: http://biz.yahoo.com/ap/080514/techbit_internet_typos.html?.v=2

2 comments May 7, 2008


Categories

Archives

RSS Click icon for your feed

Twitter Stream

Rather Receive via Email?

Recent Comments

Melissa on The 2.0 Communicator
D. Dee on The 2.0 Communicator
patrick on The 2.0 Communicator
Stephen on The 2.0 Communicator
Azmal on DIY the Answer to ABS Pro…

Tags

Advertising.com Ars Technica Bimmer Magazine BMW BMW 530 Broadband Broadbandcensus.com BT Businesswire Danny Sullivan DNS DNSSEC Drew Clark E36 Evo Bistro Facebook FCC Google GovDelivery Government 2.0 Kaminsky M3 Microsoft Monet Rims net neutrality Newsweek online advertising Pinot Noir Pizzeria Paradiso PR SaaS Saul Hansell SEO social media Strategic Communications Group tapas Tellabs TireRack Tom Claburn Washington Business Journal Washington Post WiMax Work Yahoo Yankee Group

Blogroll

Add to Technorati Favorites