ICANN ditches plan to give governments more power

ICANN has quietly abandoned a plan to make it harder for its board of directors to go against the wishes of national governments.
A proposal to make a board two-thirds super-majority vote a requirement for overruling advice provided by the Governmental Advisory Committee is now “off the table”, ICANN CEO Fadi Chehade told a US Senate committee hearing today.
The threshold, which would replace the existing simple majority requirement, was proposed last August as a result of talks in a board-GAC working group.
At the time, I described the proposal as a “fait accompli” — the board had even said it would use the higher threshold in votes on GAC advice in advance of the required bylaws change.
But now it’s seemingly gone.
The news emerged during a hearing of the Senate Committee on Commerce, Science, and Transportation today in Washington DC, which was looking into the transition of US oversight of ICANN’s IANA functions to a multi-stakeholder process.
Asked by Sen. Deb Fischer whether the threshold change was consistent with ICANN’s promise to limit the power of governments in a post-US-oversight world, Chehade replied:

You are right, this would be incongruent with the stated goals [of the IANA transition]. The board has looked at that matter and has pushed it back. So it’s off the table.

That came as news to me, and to others listening to the hearing.
The original plan to change the bylaws came in a board resolution last July.
If it’s true that the board has since changed its mind, that discussion does not appear to have been documented in any of the published minutes of ICANN board meetings.
If the board has indeed changed its mind, it has done so with the near-unanimous blessing of the rest of the ICANN community (although I doubt the GAC was/will be happy).
The public comment period on the proposal attracted dozens of responses from community members, all quite vigorously opposed to the changes.
The ICANN report on the public comments was due October 2, so it’s currently well over four months late.
UPDATE 1: An ICANN spokesperson just got in touch to say that the board decided to ditch its plan in response to the negative public comments.
UPDATE 2: Another ICANN spokesperson has found a reference to the board’s U-turn in the transcript of a meeting between the ICANN board and GAC at the Los Angeles public meeting last October. A brief exchange between ICANN chair Steve Crocker and Heather Dryden, then chair of the GAC, reads:

DRYDEN: On the issue of the proposed bylaw changes to amend them to a third — two-thirds majority to reject or take a decision not consistent with the GAC’s advice, are there any updates there that the Board would like to — the Board or NGPC? I think it’s a Board matter? Yes?
CROCKER: Yes.
Well, you’ve seen the substantial reaction to the proposal.
The reaction embodies, to some extent, misunderstanding of what the purpose and the context was, but it also is very instructive to all of us that the timing of all this comes in the middle of the broader accountability question.
So it’s — I think it’s in everyone’s interest, GAC’s interest, Board’s interest, and the entire community’s interest, to put this on hold and come back and revisit this in a larger context, and that’s our plan.

So it seems that the ICANN board did tip its hand a few months ago, but not many people, myself included, noticed.

2 Comments Tagged: bylaws, gac, iana, ICANN, senate, transition

Why you can’t register emojis in gTLDs

The popular “emoji” smiley faces are banned as gTLD domain names for technical reasons, according to ICANN.
Emojis are a form of emoticon that originated on Japanese mobile networks but are now used by 12-year-old girls worldwide due to their support on Android and iPhone operating systems.
It emerged last week that Coca-Cola has registered a bunch of smiley-face domain names under .ws, the Samoan ccTLD, for use in an billboard advertising campaign in Puerto Rico.
.ws was selected because it’s one of only a few TLDs that allow emojis to be registered. Coke is spinning its choice of TLD as an abbreviation for “We Smile”.
This got me thinking: would emojis be something new gTLD registries could start to offer in order to differentiate themselves?
Coke’s emoji domains, it turns out, are just a form of internationalized domain name, like Chinese or Arabic or Greek.
Emoji symbols are in the Unicode standard and could therefore be converted to the ASCII-based, DNS-compatible Punycode under the hood in web browsers and other software.
One of Coke’s (smiley-face).ws domain names is represented as xn--h28h.ws in the DNS.
Unfortunately for gTLD registries, ICANN told DI last night that emojis are not permitted in gTLDs.
“Emoticons cannot be used as IDNs as these code points are DISALLOWED under IDNA2008 protocol,” ICANN said in a statement.
IDNA2008 is the latest version of the IETF standard used to define what Unicode characters can and cannot appear in IDNs.
RFC 5892 specifies what can be included in an IDNA2008 domain name, eliminating thousands of letters and symbols that were permissible under the old IDNA2003 standard.
These characters were ostensibly banned due to the possibility of IDN homograph attacks — when bad guys set up spoof web sites on IDNs that look almost indistinguishable from a domain used by, for example, a bank or e-commerce site.
But Unicode, citing Google data, reckons symbols could only ever be responsible for 0.000016% of such attacks. Most homograph attacks are much simpler, relying on for example the visual similarity of I and l.
Regardless, because IDNA2008 only allows Unicode characters that are actually used in spoken human languages, and because gTLD registries are contractually obliged to adhere to the IDNA2008 technical standards, emojis are not permitted in gTLDs.
All new gTLDs have to provide ICANN with a list of the Unicode code points they plan to support as IDNs when they undergo pre-delegation testing. Asking to support characters incompatible with IDNA2008 would result in a failed test, ICANN tells us.
ICANN does not regulate ccTLDs, of course, so the .ws registry is free to offer whatever domains it wants.
However, ICANN said that emoji domains are only currently supported by software that has not implemented the newer IDN protocol:

Emoticon domains only work in software that has not implemented the latest IDNA standard. Only the older, deprecated version of the IDNA standard allowed emoticons, more or less by accident. Over time, these domains will increasingly not work correctly as software vendors update their implementations.

So Coke, while winning brownie points for novelty, may have registered a bunch of damp squibs.
ICANN also told us that, regardless of what the technical standards say, you’d never be able to apply for an emoticon as a gTLD due to the “letters only” principle, which already bans numbers in top-level strings.

5 Comments Tagged: .ws, coca-cola, emojis, iana, ICANN, idna2008, idns, unicode

Crocker caught with his pants down, literally, at ICANN 52

Here’s your daily WTF moment, courtesy of ICANN’s official YouTube account.
If you’ve ever wanted to see ICANN chair Steve Crocker without his trousers — and let’s face it, who hasn’t? — now’s your chance.

Don’t ask. I’m just as baffled as you.

3 Comments Tagged: ICANN, icann 52

Verisign sues .xyz and Negari for “false advertising”

Handbags at dawn!
Verisign, the $7.5 billion .com domain gorilla, has sued upstart XYZ.com and CEO Daniel Negari for disparaging .com and allegedly misrepresenting how well .xyz is doing.
It’s the biggest legacy gTLD versus the biggest (allegedly) new gTLD.
The lawsuit focuses on some registrars’ habit of giving .xyz names to registrants of .com and other domains without their consent, enabling XYZ.com and Negari to use inflated numbers as a marketing tool.
The Lanham Act false advertising lawsuit was filed in Virginia last December, but I don’t believe it’s been reported before now.
Verisign’s beef is first with this video, which is published on the front page of xyz.com:

Verisign said that the claim that it’s “impossible” to find a .com domain (which isn’t quite what the ad says) is false.
The complaint goes on to say that interviews Negari did with NPR and VentureBeat last year have been twisted to characterize .xyz as “the next .com”, whereas neither outlet made such an endorsement. It states:

XYZ’s promotional statements, when viewed together and in context, reflect a strategy to create a deceptive message to the public that companies and individuals cannot get the .COM domain names they want from Verisign, and that XYZ is quickly becoming the preferred alternative.

As regular readers will be aware, .xyz’s zone file, which had almost 785,000 names in it yesterday, has been massively inflated by a campaign last year by Network Solutions to push free .xyz domains into customers’ accounts without their consent.
It turns out Verisign became the unwilling recipient of gtld-servers.xyz, due to it owning the equivalent .com.
According to Verisign, Negari has used these inflated numbers to falsely make it look like .xyz is a viable and thriving alternative to .com. The company claims:

Verisign is being injured as a result of XYZ and Negari’s false and/or misleading statements of fact including because XYZ and Negari’s statements undermine the equity and good will Verisign has developed in the .COM registry.
…
XYZ and Negari should be ordered to disgorge their profits and other ill-gotten gains received as a result of this deception on the consuming public.

The complaint makes reference to typosquatting lawsuits Negari’s old company, Cyber2Media, settled with Facebook and Goodwill Industries a few years ago, presumably just in order to frame Negari as a bad guy.
Verisign wants not only for XYZ to pay up, but also for the court to force the company to disclose its robo-registration numbers whenever it makes a claim about how successful .xyz is.
XYZ denies everything. Answering Verisign’s complaint in January, it also makes nine affirmative defenses citing among other things its first amendment rights and Verisign’s “unclean hands”.
While many of Verisign’s allegations appear to be factually true, I of course cannot comment on whether its legal case holds water.
But I do think the lawsuit makes the company looks rather petty — a former monopolist running to the courts on trivial grounds as soon as it sees a little competition.
I also wonder how the company is going to demonstrate harm, given that by its own admission .com continues to sell millions of new domains every quarter.
But the lesson here is for all new gTLD registries — if you’re going to compare yourselves to .com, you might want to get your facts straight first if you want to keep your legal fees down.
And perhaps that’s the point.
Read the complaint here and the answer here, both in PDF format.

13 Comments Tagged: .com, .xyz, false advertising, new gTLDs, verisign, xyz.com

Chehade to face Congressional grilling this week

ICANN CEO Fadi Chehade is heading to Washington DC this week to defend plans to decouple the organization from formal US oversight in front of a potentially hostile committee of Congresspeople.
The Senate Committee on Commerce, Science, and Transportation will meet this Wednesday at 1000 local time to grill Chehade and others on the plan to remove the US government from the current triumvirate responsible for managing changes to the DNS root zone under the IANA arrangements.
He will be joined by Larry Strickling, who as head of the National Telecommunications and Information Administration is the US government’s point person on the transition, and Ambassador David Gross, a top DC lawyer formerly with the Department of State.
All three men are pro-transition, while the Republican-tilted committee is likely to be much more skeptical.
The blurb for the Wednesday hearing reads:

As the U.S. government considers relinquishing control over certain aspects of Internet governance to the private sector, concerns remain that the loss of U.S. involvement over the Internet Assigned Numbers Authority (IANA) could empower foreign powers — acting through intergovernmental institutions or other surrogates — to gain increased control over critical Internet functions.

Republicans and right-leaning media commentators have warned that handing over IANA oversight to a multistakeholder body risks giving too much power to governments the US doesn’t like, such as Russia and China.
Several bills introduced in the House and Senate over the last year would have given Congress much more power to delay or deny the transition.
An amendment to an appropriations bill approved in December prevents the NTIA from spending any taxpayer money on relinquishing its DNS root oversight role until after September 30 this year, the same day that the current IANA contract expires.
This effectively prevents a transition during the current IANA contract’s run. Strickling recently said that the NTIA is complying with this legislation, but noted that it does not prevent the agency participating in the development of the transition proposal.
ICANN community working groups are currently working on plans for ICANN oversight post-NTIA and for addressing ICANN accountability.
These documents are hoped to be ready to sent to the NTIA by July, so the NTIA will have enough time to consider them before September 30.
Strickling recently addressed this date in a speech at the State of the Net conference in Washington, saying:

I want to reiterate again that there is no hard and fast deadline for this transition. September 2015 has been a target date because that is when the base period of our contract with ICANN expires. But this should not be seen as a deadline. If the community needs more time, we have the ability to extend the IANA functions contract for up to four years. It is up to the community to determine a timeline that works best for stakeholders as they develop a proposal that meets NTIA’s conditions, but also works.

Opponents of the transition say that because the NTIA is prevented from terminating the IANA contract before October 1, the NTIA will have no choice but to extend it until September 30, 2017.
Given that 2016 is a presidential election year in the US, Barack Obama would be a private citizen again by the time the next opportunity to transition comes around, they say.
Which presidential hopeful — from either party — would not buckle if asked whether he supports a plan to let Iran run the internet? That’s the political logic at work here.
Chehade himself told the AFP news agency earlier this month that the transition would have to happen before the 2016 elections, to avoid political distractions.
I’m not so sure I agree with the premise that, due to the restraints imposed by the appropriation bill, the transition now has to happen under the next president’s administration.
In my layman’s reading of the current IANA contract, the NTIA is able to terminate it for the “convenience of the government” pretty much whenever it wants.
There’s also an option to extend the contract by up to six months. The NTIA exercised this option in March 2012 when it did not approve of ICANN’s first renewal proposals.

1 Comment Tagged: commerce, congress, iana, ICANN, ntia, transition

Get NamesCon 2016 tickets at 80% off

After its well-received 2015 show in Las Vegas last month, NamesCon has confirmed a third annual domain name conference for 2016 and is offering deeply discounted tickets for “super early birds” until the end of the month.
Until February 28, conference passes can be bought for $199. That’s an 80% discount on the regular $999 fee. No other early-bird discounts have yet been announced, but NamesCon says this is the “lowest” price the tickets are going to get.
As the event is targeted largely at domainers, NamesCon notes that tickets are non-transferable. Touts are not welcome, in other words.
The show will run from January 10 to 13 next year, in Las Vegas. The venue will be the reasonably priced Tropicana hotel for the third year in a row.
Conference producer Richard Lau said that the 2016 show will have a new sponsorship opportunity in the form of a “Meetery” on the first day.
With space for about 30 companies on small tables, the six-hour window will be “ideal for companies who do not want to man a booth for the entire conference but still want to be able to meet with all of the attendees,” Lau said.
NamesCon is also expanding the number of small tables available for sponsors that want to exhibit for the whole four days from six to 15 to 20, he said.
Tickets can be obtained through the NamesCon web site.

Comment Tagged: namescon

.xxx boss says new gTLD registries need to “wake up”

ICM Registry president Stuart Lawley may be just weeks away from launching his second and third gTLD registries, but that doesn’t mean he has a positive outlook on new gTLDs in general.
“I think people need to wake up,” he told DI in a recent interview. “If you do the math on some of these numbers and prospective numbers, it just doesn’t stack up for a profitable business.”
“The new ‘Well Done!’ number seems to be a lot less than it was six months ago or 12 months ago,” he said.
Lawley said he’s among the most “bearish” in the industry when it comes to new gTLD prospects. And that goes for ICM’s own .porn, .sex and .adult, which are due to launch between March and September this year.
While he’s sure they’ll be profitable, and very bullish on the search engine optimization benefits that he says registrants could be able to achieve, he’s cautious about what kind of registration volumes can be expected. He said:

If you add up everybody that has ever bought a .xxx name, including the Sunrise B defensives, we have got a target market of about 250,000 names. People to go back to and say, “Look, you still have a .xxx or you had a .xxx at some stage. Therefore, we think you may be interested in buying .porn, .sex or .adult for exactly the same reasons.”
So, our expectations to sell to a whole new market outside of those quarter of a million names is probably quite limited.

Lawley said that he believes that the relatively poor volume performance of most new gTLDs over the last year will cause many registrars to question whether it’s worth their time and money to offer them.

I can see why registrars can’t be bothered. How many of these am I going to sell? Am I going to sell two hundred of them? Am I going to make five dollars per name? That’s one thousand dollars. It’s not worth it to me to put in ten thousand dollars worth of labor and effort to make one thousand dollars in revenue. So, I think that’s a challenge that many of the small lone player TLDs may face.

Lawley said he’s skeptical about the ability of major portfolio players, such as Donuts, to effectively market their hundreds of gTLDs, many of which are targeted at niche vertical markets.
He said in an ideal world a gTLD would need to spend $20 million to $30 million a year for a few years in order to do a proper PR job on a single TLD — ICM spent about $8 million to $9 million, $5.5 million of which was on US TV spots — and that’s just not economically viable given how many names are being sold.
But he added that he thinks it’s a good thing that some new gTLDs are seeing a steady and fairly linear number of daily additions, saying it might point to better long-term stability.

A lot of the TLDs that seem to be doing okay — .club for argument’s sake and several others in that ilk — seem to be doing their three hundred domains per day ADD, or 32 or 12 or whatever the number is, in a relatively linear fashion six or seven months after launch, which I think is potentially positive if one extrapolates that out.

The full interview, which also addresses SEO, dot-brands, registrar pay-for-placement and smart search, can be read by DI PRO subscribers here.

2 Comments Tagged: .adult, .club, .sex, di pro, donuts, icm registry, new gTLDs, porn, xxx

Sex.co for sale at $200,000

Remember when sex.com sold for $13 million?
The owner of sex.co, which according to Whois is Amsterdam-based Quattro Media Co, has put the domain on the market with a buy-it-now price of $200,000.
That’s according to Heritage Auctions, which says it is managing the sale.
There are no buyer’s fees associated with the offer, HA said in an email blast.
Given there’s only one letter difference between sex.com and sex.co, you’d imagine that the .co benefits from a fair bit of typo traffic. The domain is currently parked.
For sale at less than 2% of the price that sex.com went for back in 2010, would $200,000 be a bit of a bargain?

2 Comments Tagged: heritage auctions, sex.co, sex.com

Renewals at 55% as first new gTLD junk drop begins

The first new gTLD to go live is seeing its first-year renewals at 55% one year after hitting general availability.
dotShabaka Registry’s شبكة. (or “.shabaka”, the Arabic for “.web”) has also seen its zone file shrink by about 27% over the last two weeks.
The zone peaked at 2,069 domains on February 1, 2015, but today stands at 1,521. Exactly one year ago, it was at 1,561 names.
The zone is smaller today than it was just two weeks after GA began, in other words.
“We can confirm we’re seeing renewal rates for names due in February at around 55%,” Adrian Kinderis, CEO of ARI Registry Services, which runs .shabaka’s back-end, told DI in a statement.
The registry added 1,608 domains in February 2014, 1,400 of those in the first half of the month.
The 55% is the number of domains that were renewed before their February expiry date. The full number for February will not be known until the grace period ends in mid-April.
“We have a handful of cancel renews and all other expired domains are in the auto-renew period,” he said. “It’s too early to examine the numbers for renews post-expiry date, but we expect this will increase the overall tally.”
“Given the market conditions we face in the region, the results align with our forecasts and we expect the numbers to improve for renewals due in the coming weeks and months,” he said.
In gTLDs, domains can enter a Auto Renew Grace Period for up to 45 days after expiration, during which they can still be renewed by their registrant and may or may not appear in the zone file.
It wouldn’t be fair on other new gTLD registries to read to much into these numbers, assuming they do not improve, as شبكة. is a bit of an unusual case.
It’s seen low registration volume, despite the apparently attractive string, largely because it’s restricted to Arabic script at the second level and the Arabic-speaking market is in its infancy.
When شبكة. launched there were no registrars offering an end-to-end Arabic shopping cart, Kinderis said. He added:

The most significant problem still remains demand and consumer awareness…
In regards to demand, the lack of awareness is a direct result of little to no marketing in the region. Apart from our own efforts, there has been little marketing or education programs deployed to increase awareness of new Top-Level Domains and Arabic script domain names.
We have even limited our marketing efforts because we identified early that market readiness is inadequate. Any large investment in marketing from dotShabaka Registry at the moment would be premature and wasteful until supply, demand and universal acceptance issues have been addressed.

He called on ICANN and its recently created Middle East Working Group to focus on ways to increase awareness and demand for domain names in the region. To date, it’s focused too much registrars and technical issues, he said.
شبكة. has its own set of issues and is probably not the best test case for new gTLDs in general.
That’s going to come soon. Donuts’ first batch of gTLDs — .guru, .bike, .holdings, .plumbing, .singles, .ventures and .clothing — had their base-price GA anniversary on February 4, and it appears that domains have already started to drop.
There’s little indication of anything amiss in the .guru zone file so far but the other six are down slightly — by maybe 100 or so names apiece, or less than 1% each — over the last two weeks.
Donuts executives have said they expect first-year renewals to be strong, but we’ve got a few weeks left before anyone will be in a position to know for sure.

3 Comments Tagged: .shabaka, ari, dotshabaka, ICANN, junk drop, new gTLDs, شبكة

Group forms to stop new gTLDs breaking stuff

A little over a year into the live phase of the new gTLD program, a group of domain industry companies are getting together to make sure the expansion is supported across the whole internet.
A new Universal Acceptance Steering Group has formed, with the support of ICANN and the Domain Name Association, to help fix many of the compatibility problems facing new gTLD registrants today.
“The basic problem is that these new types of domains and email addresses just break stuff,” Google’s Brent London said during a UASG meeting at the ICANN meeting in Singapore last week.
“You try to use an internationalized domain or a long new gTLD, or even a short new gTLD, or certainly an internationalized email address and you’re likely to run into problems,” he said. “What we’re doing is going around asking developers to make their products work.”
Universal acceptance is a long-understood problem. Even 15 years after the approval of .info there are still web sites that validate email addresses by ensuring the TLD is no longer than three characters in length.
But the 2012 new gTLD round has brought the issue into sharper focus, particularly given the introduction of internationalized domain names, IDNs, which use non-Latin scripts.
Over the last year we’ve seen scattered examples of popular software — including browsers, instant messaging and social media apps — not recognizing new gTLD domains as domains. The problems I’ve seen are usually fixed quite quickly.
While I’ve not seen any deal-breakers that would prevent me registering a new gTLD domain, I gather that IDN email addresses are often basically unusable, due to the chain of dependencies involved in sending an email.
In my experience as a programmer, supporting all TLDs is not a particularly challenging problem when you’re coding something afresh.
However, when bad practices have been coded in to large, sprawling, interdependent systems over decades, it could be likened to the Y2K problem — the so-called Millennium Bug that caused developer headaches worldwide at the end of the last century.
There’s also a tonne of bad advice on the web, with coders telling other coders to validate domains in ways that do not support an expanding root.
UASG members think the problem is large-scale and that it’s a long-term project — 10 years or more — to fix it satisfactorily.
Members include Donuts, Google, Microsoft, Go Daddy and Afilias.
The DNA has started creating a repository of information for developers, with the aim of describing the problem in plain English and providing code samples. Along with other UASG members, there’s a plan to conduct outreach to make more people aware of the acceptance issue.
You can check out the repository in its unfinished state here.
ICANN is getting involved in a coordination role. After the UASG’s inaugural meeting in Washington DC a few weeks ago, ICANN hosted a session during ICANN 52.
It’s also hosting a mailing list and the group’s first conference call, which will take place tomorrow at 1600 UTC.

3 Comments Tagged: ICANN, icann 52, new gTLDs, the dna, uasg, universal acceptance