There are over 1,000 new gTLDs out there right now, and figuring out what’s going on in the marketplace can be difficult.
So what better way to reduce confusion than to plot the 250 most populous TLDs into an infographic that vaguely resembles the iconic London Underground route map?
There must be thousands of better ways.
Regardless, the Tube map idea is the one Nominet decided to run with, and it released this beauty today.
While the strings have been roughly organized by categories, there doesn’t seem to be much logic to the layout otherwise.
If one were to overlap the map on a map of London, there doesn’t appear to be much relationship between the string and the characteristics of the corresponding neighborhood.
DI World International Global Headquarters would be sandwiched between .lawyer and .marketing, or thereabouts, just to the north of Jack the Ripper’s stalking ground of .miami.
There is a Citizens Advice Bureau across the street, but I’m not sure that makes this area a hotbed of legal activity.
Market-leading .xyz would be up in Walthamstow somewhere, quite off the beaten track, .tokyo would be close to Chinatown, and .city is nowhere near the City.
I’m probably reading it wrong.
Registry operators are challenging an ICANN decision to force them to launch a new Whois-style service, saying it will cost them too much money.
The Registries Stakeholder Group has filed a Request for Reconsideration — a low-level appeal — of a decision asking them to launch RDAP services to complement their existing Whois.
RDAP, Registration Data Access Protocol, is being broadly touted as the successor to Whois.
It offers the same functionality — you can query who owns a domain — but the data returned is more uniformly structured. It also enables access control, so not every user would have access to every field.
The RySG now claims that ICANN is trying to sneak an obligation to implement RDAP into its registry agreements through a “backdoor” in the form of the new Consistent Labeling and Display Policy.
That policy, which originated in a formal, community-driven GNSO Policy Development Process, seeks to normalize Whois (or Registration Data Services, in its generic not protocol-specific wording) output to make it easier to machine-read.
It applies to all gTLDs except .com, .net and .jobs (which are “thin” registries) and would come into effect February 1 next year.
Registries appear happy to implement the CL&D policy, but not as currently written. It now contains, almost as an aside, this requirement:
The implementation of an RDAP service in accordance with the “RDAP Operational Profile for gTLD Registries and Registrars” is required for all gTLD registries in order to achieve consistent labeling and display.
The RySG argues in its RfR (pdf) that implementing RDAP was never part of the community-endorsed plan, and that it is not “commercially feasible” to do so right now.
The 2012 new gTLD Registry Agreement specifies that implementation of the protocol now known as RDAP be commercially feasible before it’s required. The RySG can’t even respond as to whether it’s feasible or not since no reasoning to that regard was provided in the notice to implement such services.
Furthermore, some of our members are on record stating that since the RDAP profile replicates the known deficiencies of WHOIS – which is currently being studied by a PDP WG – so it’s not commercially feasible to deploy it to mimic a flawed system.
The introduction of RDAP represents an additive requirement for Registries to operate a new (additive) service. As there are no provisions for the sunset of the legacy Whois service, it’s unclear how this additional requirement can be considered commercially feasible.
In other words, the registries think it could be too costly to deploy RDAP and Whois at the same time, especially given that RDAP is not finished yet.
It’s yet another case of domain companies accusing ICANN the organization of slipping in requirements without community support.
Whether the RfR will be successful is debatable. There’s only been a few Reconsideration requests that have been approved by the ICANN board in the history of the mechanism.
However, the board may be feeling especially diligent when it comes to look at this particular RfR, due to the spotlight that was recently shone on the Reconsideration process by an Independent Review Process panel, which determined that the board just rubber-stamped decisions written by house lawyers.
NamesCon says it has booked the venue for three more years of domain name conferences, following its acquisition this week.
The conference organizers said today that it has been acquired by 13-year-old German events outfit WorldHostingDays, which usually focuses on the hosting market, for an undisclosed sum.
NamesCon said in a press release that all existing commitments — such as tickets and sponsorship deals — will be honored, and that the same folk will still run the 2017 conference.
It said that it has booked the Tropicana hotel in Las Vegas, venue for the first three events, for the next three years.
The next three events will be held January 22 – 25, 2017, January 28 – 31, 2018 and January 27 – 30, 2019, the company said.
NamesCon focuses on the business of domain names, providing sessions on the buy and sell sides of the business.
Afilias is back on the path to becoming the registry for .hotel, after ICANN decided claims of hacking by a former employee of the applicant did not warrant a rejection.
The ICANN board of directors decided last week that HOTEL Top-Level Domain Sarl, which was recently taken over by Afilias, did not gain any benefit when employee Dirk Krischenowski accessed competing applicants’ confidential documents via an ICANN web site.
Because HTLD had won a Community Priority Evaluation, it should now proceed to contracting, barring any further action from the other six applicants.
ICANN’s board said in its August 9 decision:
ICANN has not uncovered any evidence that: (i) the information Mr. Krischenowski may have obtained as a result of the portal issue was used to support HTLD’s application for .HOTEL; or (ii) any information obtained by Mr. Krischenowski enabled HTLD’s application to prevail in CPE.
It authorized ICANN staff to carry on processing the HTLD application.
The other applicants — Travel Reservations, Famous Four Media, Radix, Minds + Machines, Donuts and Fegistry — had called on ICANN in April to throw out the application, saying that to decline to do so would amount to “acquiescence in criminal acts”.
That’s because an ICANN investigation had discovered that Dirk Krischenowski, who ran a company with an almost 50% stake in HTLD, had downloaded hundreds of confidential documents belonging to competitors.
He did so via ICANN’s new gTLD applicants’ portal, which had been misconfigured to enable anyone to view any attachment from any application.
Krischenowski has consistently denied any wrongdoing, telling DI a few months ago that he simply used the tool that ICANN made available with the understanding that it was working as intended.
ICANN has now decided that because the unauthorized access incidents took place after HTLD had already submitted its CPE application, it could not have gained any benefit from whatever data Krischenowski managed to pull.
The board reasoned:
his searches relating to the .HOTEL Claimants did not occur until 27 March, 29 March and 11 April 2014. Therefore, even assuming that Mr. Krischenowski did obtain confidential information belonging to the .HOTEL Claimants, this would not have had any impact on the CPE process for HTLD’s .HOTEL application. Specifically, whether HTLD’s application met the CPE criteria was based upon the application as submitted in May 2012, or when the last documents amending the application were uploaded by HTLD on 30 August 2013 – all of which occurred before Mr. Krischenowski or his associates accessed any confidential information, which occurred from March 2014 through October 2014. In addition, there is no evidence, or claim by the .HOTEL Claimants, that the CPE Panel had any interaction at all with Mr. Krischenowski or HTLD during the CPE process, which began on 19 February 2014.
The HTLD/Afilias .hotel application is currently still listed on ICANN’s web site as “On Hold” while its rivals are still classified as “Will Not Proceed”.
It might be worth noting here — to people who say ICANN always tries to force contention sets to auction so it possibly makes a bit of cash — that this is an instance of it not doing so.
Blogging pioneer Dave Winer has become the first person to start blogging at a .blog domain name.
His new site, dave.blog, went live yesterday as a beneficiary of registry Knock Knock Whois There’s pioneer program.
The site is one of two pioneer .blog domains — the other being design.blog — highlighted by KKWT yesterday in publicity connected to the opening of its sunrise period.
Winer is the author of Scripting News, which has been around since 1997, one of the first must-read tech blogs.
He also made major contributions to the format and popularity of RSS syndication technology.
He was an outspoken critic of Google, which had planned to use blog in a “closed generic” fashion, linked closely to its Blogger service, writing in 2012:
I played a role in establishing blogs. How does Google get the right to capture all the goodwill generated in the word blog?
Yesterday he expressed relief that the .blog auction was actually won by KKWT, a subsidiary of WordPress owner Automattic, writing:
I’m glad to say that my friend Matt Mullenweg and Automattic are consistent champions of user and developer freedom. That’s why they host .blog for all to use. They could have said “blog” == “wordpress” — many companies would have — but they didn’t. That’s very good! I wish more big tech companies had that philosophy.
Winer said he will use his self-developed 1999.io blogging software on his new domain.
His allocation of dave.blog is arguably bad news for blokey British cable TV station Dave and disgraced former prime minister David “Call Me Dave” Cameron.