While attending the International Telecommunications Society's 17th bi-annual conference I attended yet another network neutrality session. Economists predominated at this conference and their collective read on network neutrality emphasizes the need for ISPs to "extract value" from content providers primarily by converting zero cost peering with ISPs into specific payments from individual content sources. I have no problem with offers of non-neutral, "better than best efforts" routing options to content providers who voluntarily opt in, particularly if the offer is made transparently and anyone can opt in. What troubles me is the impact of opt-in on content providers that opt out...
More than 40 years ago, the FCC was worried about telephone companies using their power over communications to control the then-nascent (and competitive) data processing marketplace. The Bell System at that point was already banned from providing services that weren't common carriage communications services (or "incidental to" those communications services)... In a 1999 article in the Texas Law Review, Steve Bickerstaff pointed out that Computer 1 meant that no one could provide a "computer utility" service... Today, we'd call the "computer utility" something different -- we'd use the term "cloud computing."
I've watched coverage of Microsoft's bid for Yahoo! and the related maneuvering between Google and Yahoo!. The explanations are not very convincing. Microsoft doesn't need Yahoo's search technology or their morale-impacted work force. Yahoo's search market share continues to decline and there's little of strategic relevance in the rest of their business. What's the attraction?
Lost amid the furor about ICANN's rule change that may (or may not) lead to a flood of TLDs is the uncomfortable fact that almost without exception, the new TLDs created since 2000 have been utter failures. Other than perhaps .cat and .mobi, they've missed their estimates of the number of registrations by orders of magnitude, and they haven't gotten mindshare in the target community. So what went wrong?
The recent decision by ICANN to start a new round of applications for new generic Top-Level Domains (gTLDs) is launching a round of questions on the IETF side about its consequences. One possible issue may be with vanity gTLDs like apple, ebay etc. Some expect that every Fortune 1,000,000 company will apply for its own TLD. My guess is rather the Fortune 1,000 for a start, but this does not change the nature of the issue, i.e. those companies may want to use email addresses like user@tld.
Some offhand comments by Google's Vint Cerf at a recent event seem to have a triggered a panicky "Vint Cerf proposes nationalizing the Internet" buzz that's been ramping up fairly rapidly. Holy BitTorrent, Batman! Army paratroopers seen dropping into parking lots at AT&T and Comcast, while the Transportation Security Agency orders us all to remove our shoes before surfing the Web! Settle down, everyone. As usual with these kinds of stories, the truth is significantly different from the breathless buzzing. Here's how Vint described his thinking on this issue to me...
In all the recent uproar (New York Times, "Google Told to Turn Over User Data of YouTube," Michael Helft, 4 July 2008) about the fact that Google has been forced to turn over a large pile of personally-identifiable information to Viacom as part of a copyright dispute (Opinion), there is a really interesting angle pointed out by Dan Brickley (co-creator of FOAF and general Semantic Web troublemaker)...
At its 32d International Junket Meeting last week, ICANN's Board approved the GNSO Council's recommendations for the eventual addition to the root of new generic top-level domains (gTLDs). This means that eventually, when the staff drafts, community comments upon, and Board approves implementation processes, those with deep pockets will have the opportunity to bid for new TLD strings...
Both the Internet and North American cellphones are choking under a 32 bit limitation and reactions from protagonists involved in both cases offer striking similarities. 1983 saw the debut of IPv4 and North American mobile telephony started in earnest with Bell's analog AMPS (Advanced Mobile Phone Service). Responding to the need to uniquely identify the growing number of mobile devices in order to bill their owner, the FCC ordered that handsets be equipped with a unique identification number embedded on a chip. This became the 32 bit ESN...
In this article I will explain the motivations behind the SocialDNS Project. I will justify why the DNS system is NOT the phone book of the Internet. More concretely, DNS is not a public directory nor enables search mechanisms over meta-information related to domains. In this line, I will present the advantages of SocialDNS, a naming and directory system that aims to become the phone book of the Web. SocialDNS is NOT another alternative DNS root nor aims to replace the current DNS for resolving domain names. It complements the existing DNS to offer advanced services that are beyond the scope of the existing infrastructure for Web settings.