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.
The CEO of Turkey’s largest registrar is facing terrorism charges in the wake of last month’s coup attempt in the country, according to reports.
Abdullah Büyük of Istanbul-based FBS was deported from Bulgaria last Wednesday, according to local reports, having overstayed his visa.
Büyük went to Bulgaria last year and Turkey had unsuccessfully tried to get him extradited earlier this year.
Turkey’s Erdogan government, which has arrested thousands of people since the July 15 attempted coup, claims Büyük is a supporter of US-based exiled cleric Fethullah Gülen.
Turkey claims that Gulen is behind a terrorist group called FETÖ, which it believes carried out the attack.
Buyuk is reportedly an open supporter of Gulen, but it’s not entirely clear from English-language reports out there what he’s accused of doing.
I suspect it’s probably unrelated to domain names.
The decision to hand over Buyuk to Turkish authorities has proved controversial in Bulgaria, where some suspect it was a political gesture related to Europe’s migrant crisis.
FBS is believed to be Turkey’s largest registrar, with just shy of 600,000 domain names under management.
Some of Verisign’s chickens have evidently come home to roost.
A number of companies that the registry giant has pissed off over the last couple of years have slammed the proposed renewal of its .com contract with ICANN.
Rivals including XYZ.com (sued over its .xyz advertising) and Donuts (out-maneuvered on .web) are among those to have filed comments opposing the proposed new Registry Agreement.
They’re joined by business and intellectual property interests, concerned that Verisign is being allowed to carry on without implementing any of the IP-related obligations of other gTLDs, and a dozens of domainers, spurred into action by a newsletter.
Even a child protection advocacy group has weighed in, accusing Verisign of not doing enough to prevent child abuse material being distributed.
ICANN announced last month that it plans to renew the .com contract, which is not due to expire for another two years, until 2024, to bring its term in line with Verisign’s contracts related to root zone management.
There are barely any changes in the proposed new RA — no new rights protection mechanisms, no changes to how pricing is governed, and no new anti-abuse provisions.
The ensuing public comment period, which closed on Friday, has attracted slightly more comments than your typical ICANN comment period.
That’s largely due to outrage from readers of the Domaining.com newsletter, who were urged to send comments in an article headlined “BREAKING: Verisign doubles .COM price overnight!”
That headline, for avoidance of doubt, is not accurate. I think the author was trying to confer the idea that the headline could, in his opinion, be accurate in future.
Still, it prompted a few dozen domainers to submit brief comments demanding “No .com price increases!!!”
The existing RA, which would be renewed, says this about price:
The Maximum Price for Registry Services subject to this Section 7.3 shall be as follows:
(i) from the Effective Date through 30 November 2018, US $7.85;
(ii) Registry Operator shall be entitled to increase the Maximum Price during the term of the Agreement due to the imposition of any new Consensus Policy or documented extraordinary expense resulting from an attack or threat of attack on the Security or Stability of the DNS, not to exceed the smaller of the preceding year’s Maximum Price or the highest price charged during the preceding year, multiplied by 1.07.
The proposed amendment (pdf) that would extend the contract through 2024 does not directly address price.
It does, however, contain this paragraph:
Future Amendments. The parties shall cooperate and negotiate in good faith to amend the terms of the Agreement (a) by the second anniversary of the Effective Date, to preserve and enhance the security and stability of the Internet or the TLD, and (b) as may be necessary for consistency with changes to, or the termination or expiration of, the Cooperative Agreement between Registry Operator and the Department of Commerce.
The Cooperative Agreement is the second contract in the three-way relationship between Verisign, ICANN and the US Department of Commerce that allows Verisign to run not only .com but also the DNS root zone.
It’s important because Commerce exercised its powers under the agreement in 2012 to freeze .com prices at $7.85 a year until November 2018, unless Verisign can show it no longer has “market power”, a legal term that plays into monopoly laws.
So what the proposed .com amendments mean is that, if the Cooperative Agreement changes in 2018, ICANN and Verisign are obligated to discuss amending the .com contract at that time to take account of the new terms.
If, for example, Commerce extends the price freeze, Verisign and ICANN are pretty much duty bound to write that extension into the RA too.
There’s no credible danger of prices going up before 2018, in other words, and whether they go up after that will be primarily a matter for the US administration.
The US could decide that Verisign no longer has market power then and drop the price freeze, but would be an indication of a policy change rather than a reflection of reality.
The Internet Commerce Association, which represents high-volume domainers, does not appear particularly concerned about prices going up any time soon.
It said in its comments to ICANN that it believes the new RA “will have no effect whatsoever upon the current .Com wholesale price freeze of $7.85 imposed on Verisign”.
XYZ.com, in its comments, attacked not potential future price increases, but the current price of $7.85, which it characterized as extortionate.
If .com were put out to competitive tender, XYZ would be prepared to reduce the price to $1 per name per year, CEO Daniel Negari wrote, saving .com owners over $850 million a year — more than the GDP of Rwanda.
ICANN should not passively go along with Verisign’s selfish goal of extending its unfair monopoly over the internet’s most popular top-level domain name.
Others in the industry chose to express that the proposed contract does not even attempt to normalize the rules governing .com with the rules almost all other gTLDs must abide by.
Donuts, in its comment, said that the more laissez-faire .com regime actually harms competition, writing:
It is well known that new gTLDs and now many other legacy gTLDs are heavily vested with abuse protections that .COM is not. Thus, smaller, less resource-rich competitors must manage gTLDs laden (appropriately) with additional responsibilities, while Verisign is able to operate its domains unburdened from these safeguards. This incongruence is a precise demonstration of disparate treatment, and one that actually hinders effective competition and ultimately harms consumers.
It points to numerous statistics showing that .com is by far the most-abused TLD in terms of spam, phishing, malware and cybersquatting.
The Business Constituency and Intellectual Property Constituency had similar views about standardizing rules on abuse and such. The IPC comment says:
The continued prevalence of abusive registrations in the world’s largest TLD registry is an ongoing challenge. The terms of the .com registry agreement should reflect that reality, by incorporating the most up-to-date features that will aid in the detection, prevention and remediation of abuses.
The European NGO Alliance for Child Safety Online submitted a comment with a more narrow focus — child abuse material and pornography in general.
Enasco said that 41% of sites containing child abuse material use .com domains and that Verisign should at least have the same regulatory regime as 2012-round gTLDs. It added:
Verisign’s egregious disinterest in or indolence towards tackling these problems hitherto hardly warrants them being rewarded by being allowed to continue the same lamentable
I couldn’t find any comments that were in unqualified support of the .com contract renewal, but the lack of any comments from large sections of the ICANN community may indicate widespread indifference.
The full collection of comments can be found here.