A trio of Chinese techies have proposed a new IETF standard to enable governments to break up the Domain Name System along national borders.
Named “DNS Extension for Autonomous Internet (AIP)”, the spec describes a way to operate alternate DNS root servers within national boundaries using gateways for translation.
For internet users subscribed to one of these “AIP” networks, DNS requests would carry an extra TLD, such as .a or .b, to flag the fact that the requests are headed for an alternate root:
Domain node “www.yahoo.com” in network B is expressed as “www.yahoo.com.B” for its external domain name.
Written in broken English, the Internet Draft is a poorly masked description of a way to install government censorship via officially sanctioned domain name system Balkanization.
It appears to be designed to enable governments to cut ICANN and the authoritative DNS root out of the picture entirely in favor of a national peering system more akin to traditional telecoms networks.
The paper reads:
In order to realize the transition from Internet to Autonomous Internet, each partition of current Internet should first realize possible self-government and gradually reduce its dependence on the foreign domain names, such as COM, NET et al.
It is not likely the whole Internet can be transformed synchronally in one time. In order not to affect existing domain name resolution before the Internet core part transforms into an AIP network, any country can set up an AIP DNS independently and connect to the Internet through the original link; or any two countries in agreement can set up their AIP networks and connect to each others.
The paper was written by Yuping Diao of Guangdong Commercial College, Yongping Diao of China Telecom and Ming Liao of China Mobile.
It’s just an Internet Draft at this stage, and probably nothing to get too worked up about, but it does reflect the Bigger Picture framing the ICANN expansion of the DNS.
During the ITU’s World Conference on International Telecommunications this December, backwards governments are expected to proposed a greater degree of government control over the internet.
ICANN’s top brass have sent personal apologies to the people whose home addresses were exposed when it published their new gTLD applications last week.
The organization blamed “human error” and said it is now conducting an “investigation” to figure out what went wrong.
The note, which is signed by CEO Rod Beckstrom, chairman Steve Crocker, and COO Akram Atallah, reads:
Dear [name of the affected executive],
On behalf of ICANN, we want to personally apologize for our error in exposing your postal address on the TLD Application website. This was a human error, and we have corrected it. We are conducting an internal investigation in order to learn from this mistake and to ensure that it does not happen again.
In the meantime, please be assured that the New Generic Top-level Domain Program remains on track. We are moving ahead with the screening and evaluation of applications, and returning to our shared goal of bringing competition and choice to the Internet’s domain name space.
We are committed to serving you to the very best of our ability and to ensuring the integrity of the New gTLD Program. If you have questions or concerns, please don’t hesitate to reach out to us directly.
As I blogged last week, ICANN accidentally neglected to redact the home addresses of many applicants’ named primary and secondary contacts when it published all 1,930 applications last week.
It has since removed the offending information.
Who the hell advised these guys?
Mitek USA, a maker of prefabricated building components (hinges, brackets, etc), has applied for four new generic top-level domains with the shoddiest applications I’ve seen so far.
For pretty much every question that requires any thought to answer, the company has simply replied “TLD will not be resold. Purchased for brand protection only.”
The phrase appears 13 times in each of the four applications.
The applications — for .mitek, .connectors, .sapphire (a brand) and .mii — therefore all appear to be a colossal waste of money.
With no answers to any technical questions beyond “TLD will not be resold. Purchased for brand protection only”, there’s no way they can pass the technical portion of the Initial Evaluation.
The bids, therefore, are completely useless. Even if the strings had been contended (they’re not), there’s no advantage to having a horse in the race if it’s guaranteed to fall at the first fence.
I ask again: who the hell advised these guys?
The top five registry back-end providers account for almost 72% of all new generic top-level domain applications, according to DI’s preliminary numbers.
Neustar, Demand Media, Afilias, Verisign and ARI Registry Services take the top five spots in our new market share league table (see below).
Thirty-eight companies are listed as back-end providers (including those that plan to self-host their gTLDs) according to our initial analysis of ICANN’s 1,930 applications.
Big portfolio applicants obviously skew the numbers significantly.
All of the 101 applications naming Google as the back-end are from Google’s own subsidiaries, and Amazon’s 76 bids are responsible for Neustar’s position at the top of the table.
Likewise, more than 300 of Demand Media’s strings are associated with one client, Donuts, and 54 of Internet Systems Consortium’s 58 are from Uniregistry, the new Frank Schilling venture.
ARI (.au) is the most successful back-end from the ccTLD world, with 160 applications, followed by Minds + Machines (.fm) with 91, CentralNic (.la) with 60 and Afnic (.fr) with 17.
|ARI Registry Services||160||8.29|
|Minds + Machines||87||4.50|
|Thai Name Server Co||1||0.05|
The four N/A applications on the list were all filed by the same poorly advised applicant.
Some numbers differ slightly from what the respective companies announced. In some cases this could be accounted for by applicants withdrawing bids before Reveal Day.
The data above was generated semi-automatically from the DI PRO New gTLD Application Database, which matches each application to its back-end, and is preliminary in nature.
A full report will follow in due course.
UPDATE (June 19): Three applications originally assigned to KSRegistry have now been reassigned to Registry.net.
UPDATE (June 20): Four applications originally assigned to Minds + Machines have been reassigned to Neustar.
I’m excited to announce the launch of a comprehensive new gTLD application tracking service, featuring a unique built-in string similarity checker, right here on DI.
The service will provide the foundation for all of DI’s new gTLD program analysis over the coming months and years, and is designed to bring together all the best information about each application under one roof.
All 1,930 applications can currently be searched and sorted by applicant, string, back-end registry provider, and status.
Users can also cross-reference applications in contention sets and read salient extracts from each application.
The gTLD application database will shortly be linked to the existing PROfile service, meaning DI PRO subscribers will have access to a database of over 3,000 domain name industry companies.
More features and bid-by-bid analysis will be added as the program progresses, but the feature I’m most excited about today is the string similarity checker, which is already built into every application profile.
This tool checks for visual and phonetic similarity with other applications, existing gTLDs and ccTLDs, as well as strings that are specially protected by the ICANN Applicant Guidebook.
Semantic similarity functionality will be added in the next few days.
Similarity is important for two reasons:
1) the String Similarity Panel, which will create new contention sets based on similar but not identical strings in a couple of months, and
2) the String Confusion Objection, which enables applicants to force rivals into the same contention set based on visual, aural or semantic similarity.
In testing, it’s already thrown up some possible future objections and contention sets that I had not previously considered, and early beta testers — applicants themselves — tell me they think it’s fantastic.
Here’s a screenshot from one of the .sex applications, to give you a taste.
Note that, unfortunately, the string similarity feature does not currently support the relatively small number of IDN string applications.
If you’re not already a DI PRO subscriber, you can sign up instantly here using PayPal. If you have any questions about the service, please email email@example.com.