Neustar’s .co contract up for grabs

Colombia is looking for a registry operator for its .co ccTLD.
If you’re interested, and you’re reading this before noon on Wednesday November 6 and you’re at ICANN 66 in Montreal, hightail it to room 514A for a presentation from the Colombian government that will be more informative than this blog post.
Hurry! Come on! Move it!
The Ministry of Information Technology and Communications (MinTIC) has published a set of documents describing some of the plan to find a potentially new home for .co.
There doesn’t appear to be a formal RFP yet, but I gather one is imminent.
What the documents do tell us is that Neustar’s contract to run .co expires in February, and that MinTIC is looking into the possibility of a successor registry.
Currently, .co is delegated to .CO Internet, a Colombian entity that relaunched the TLD in 2010 and was acquired by Neustar for $109 million in 2014.
But under a law passed earlier this year, it appears as if MinTIC is taking over policy management for .co and may therefore seek IANA redelegation.
There’s no indication I could see that there’s a plan to reverse the policy of allowing anyone anywhere in the world to register a .co, indeed MinTIC seems quite proud of its international success.
The documents also give us the first glimpse for years into .co’s growth.
It had 2,374,430 names under management in September, after a couple of years of slowing growth. The documents state that .co had an average of 323,590 new regs per year for the first seven years, which has since declined to an average of 32,396.
.co is not the cheapest TLD out there, renewing at around $25 at the low end.

Another victory for Amazon as ICANN rejects Colombian appeal

Amazon’s application for .amazon has moved another step closer to reality, after ICANN yesterday voted to reject an appeal from the Colombian government.
The ICANN board of directors voted unanimously, with two conflict-related abstentions, to adopt the recommendation of its Board Accountability Mechanisms Committee, which apparently states that ICANN did nothing wrong when it decided back in May to move .amazon towards delegation.
Neither the board resolution nor the BAMC recommendation has been published yet, but the audio recording of the board’s brief vote on Colombia’s Request for Reconsideration yesterday can be found here.
As you will recall, Colombia and the seven other governmental members of the Amazon Cooperation Treaty Organization have been trying to stymie Amazon’s application for .amazon on what you might call cultural appropriation grounds.
ACTO governments think they have the better right to the string, and they’ve been trying to get veto power over .amazon’s registry policies, something Amazon has been strongly resisting.
Amazon has instead offered a set of contractual Public Interest Commitments, such as giving ACTO the ability to block culturally sensitive strings, in the hope of calming the governments’ concerns.
These PICs, along with Amazon’s request for Spec 13 dot-brand status, will likely be published for 30 days of public comment this week, Global Domains Division head Cyrus Namazi told the board.
Expect fireworks.
After comments are closed, ICANN will then make any tweaks to the PICs that are necessary, before moving forward to contract-signing with Amazon, Namazi .said.

The Amazon is burning. Is this good news for .amazon?

With the tide of international opinion turning against Brazil due to the ongoing forest fires in the Amazon, could we see governments change their tune when it comes to Amazon’s application for .amazon?
A much higher number of forest fires than usual are currently burning in the region, largely in Brazil, which critics led by environmentalists and French president Emmanuel Macron have blamed on relaxed “slash and burn” farming policies introduced by new Brazilian president Jair Bolsonaro.
The rain forest is an important carbon sink, said to provide 20% of the world’s oxygen. The more of it is lost, the harder it is to tackle climate change, the argument goes.
It’s been an important topic at the Macro-hosted G7 summit, which ends today. Even the bloody Pope has weighed in.
Arguably, the stakes are nothing less than the survival of human civilization and life on Earth itself.
And this is a story about domain names. Sorry. This is a blog about domain names. My hands are tied.
Amazon the company has been fighting governments over its application for .amazon, along with the Chinese and Japanese translations, for over six years.
ICANN’s Governmental Advisory Committee was responsible for killing off .amazon in 2013 after it decided by consensus that Amazon’s application should not proceed.
That decision was only reached after the US, under the Obama administration, decided to abstain from discussions.
The US had been protecting Amazon by blocking GAC consensus, but changed its tune partly in order to throw a bone to world leaders, including then-president of Brazil Dilma Rousseff, who were outraged by CIA analyst Edward Snowden’s revelations of widespread US digital espionage.
After ICANN dutifully followed the GAC advice and rejected Amazon’s gTLD applications, Amazon appealed via the Independent Review Process and, in 2017, won.
The IRP panel ruled that the GAC’s objection had no clear grounding in public policy that could be gleaned from the record. It told ICANN to re-open the applications and evaluate them objectively.
Ever since then, the GAC’s advice to ICANN has been that it must “facilitate a mutually acceptable solution” between Amazon and the eight nations of the Amazon Cooperation Treaty Organization.
ICANN has been doing just that, or at least attempting to, for the last couple of years.
But the two parties failed to come to an agreement. ACTO wants to have essential veto power over Amazon’s use of .amazon, whereas Amazon is only prepared to offer lists of protected names, a minority position in any policy-setting body, and some sweeteners.
In May this year, ICANN’s board of directors voted to move .amazon along towards delegation, noting that there was “no public policy reason” why it should not.
In June, the government of Colombia filed a Request for Reconsideration with ICANN, demanding it reevaluate that decision.
The RfR was considered by ICANN’s Board Accountability Measures Committee at its meeting August 14, but its recommendation has not yet been published. I’m expecting it to be posted this week.
There’s still opportunity for the GAC to cause mischief, or act as a further delay on .amazon, but will it, in light of some country’s outrage over Brazil’s policy over the rain forest?
One could argue that if the nation that has the largest chunk of Amazon within its borders seems to have little regard to its international importance, why should its claim to ownership of the string “amazon” get priority over a big brand that has offered to protect culturally significant words and phrases?
Remember, as the example of the US in 2012/13 shows us, it only takes one government to block a GAC consensus. If Brazil or Peru continue to pursue their anti-Amazon path, could France throw a spanner in the works, smoothing .amazon’s road to delegation?
Anything’s possible, I suppose, but my feeling is that most governments back ACTO’s position largely because they’re worried that they could find themselves in a similar position of having to fight off an application for a “geographic” string in the next gTLD application round.

.amazon frozen AGAIN as endless government games continue

Amazon’s application for the .amazon gTLD has yet again been frozen, after a South American government invoked ICANN’s appeals process.
The bid, as well as applications for the Chinese and Japanese versions, were returned to “on-hold” status at the weekend, after Colombia filed a formal Request for Reconsideration, an ICANN spokesperson confirmed to DI.
“The processing toward contracting of the .AMAZON applications has been halted pending the resolution of Request 19-1, per ICANN organization’s normal processes,” the spokesperson said.
This means the applications could remain frozen for 135 days, until late October, while ICANN processes the request. It’s something that has happened several times with other contested gTLDs.
Colombia filed RfR 19-1 (pdf) on June 15. It demands that ICANN reverses its board’s decision of May 15, which handed Amazon a seemingly decisive victory in its long-running battle with the eight governments of the Amazon Cooperation Treaty Organization.
ACTO’s members believe they should have policy control over .amazon, to protect the interests of their citizens who live in the region they share.
To win an RfR — something that hardly ever happens — a complainant has to show that the ICANN board failed to consider pertinent information before it passed a resolution.
In Colombia’s case, it argues that the board ignored an April 7 letter (since published in PDF format here) its Governmental Advisory Committee representative sent that raises some interesting questions about how Amazon proposes to operate its TLDs.
Because .amazon is meant to be a highly restricted “dot-brand” gTLD, it would presumably have to incorporate Specification 13 into its ICANN registry agreements.
Spec 13 releases dot-brands from commitments to registrar competition and trademark protection in exchange for a commitment that only the brand itself will be able to own domains in the TLD.
But Colombia points out that Amazon’s proposal (pdf) to protect ACTO governments’ interests would give the eight countries and ACTO itself “beneficial ownership” over a single domain each (believed to be names such as co.amazon, .br.amazon, etc).
If this means that Amazon would not qualify for Spec 13, it could follow that ICANN’s board made its decision to continue processing .amazon on faulty assumptions, Colombia argues.
Colombia points to the case of .sas, a dot-brand that is apparently shared by two companies that have the same brand, as a possible model for shared management of .amazon.
RfRs are handled by ICANN’s Board Accountability Mechanisms Committee.
BAMC took just a couple of days to rule out (pdf) Colombia’s request for “urgent reconsideration”, which would reduce its regular response time from 90 days to 7 days.
The committee said that because the .amazon applications were being placed back on-hold as part of normal procedure during consideration of an RfR, no harm could come to Colombia that would warrant “urgent” reconsideration.
According to ICANN’s spokesperson, under its bylaws the latest the board can respond to Colombia’s request is October 28.
At a GAC session at the ICANN 65 meeting in Marrakech, taking place right now, several ACTO governments have just spent over an hour firmly and publicly protesting ICANN’s actions surrounding .amazon.
They’re still talking as I hit “publish” on this post.
In a nutshell, they believe that ICANN has ignored GAC advice and reneged on its commitment to help Amazon and ACTO reach a “mutually acceptable solution”.

Drunk domain blogger gets mugged in Cartagena

ICANN people love defining things, and a few people at the meeting here in Cartagena have disputed whether this anecdote meets the strict definition of “mugging”.
Okay, I didn’t wind up with a knife in my ribs, they weren’t carrying firearms, and they didn’t get my wallet.
But they were going to beat me up (at the very least) if I didn’t give them what they wanted and it’s really just blind luck that I managed to blag my way out of it.
I often find that these kinds of stories are better related in first-person present tense.
So it’s 4am, and I’m blatantly flouting ICANN’s security advice by walking, rather than getting a taxi, back from .CO Internet’s rather nice afterparty to my considerably less-nice hotel.
But it’s only two or three short blocks, and I’m inside the walled city, so I reckon I’m safe.
Wrong.
Two thuggish-looking blokes quickly appear beside me and one of them starts mouthing off in unusually good English about how I owe him money for a coke deal I’m apparently somehow implicated in.
I’m not kidding.
I forget the details, but the gist of it is that I need to give them both an unspecified large amount of money for some drugs that I stole or something and that Bad Things will happen to my face if I refuse.
Unfortunately for the Escobar brothers, it turns out that at 4am, with half a bottle of Colombian fire-water in my belly, I’m invincible.
Or believe myself to be, anyway.
So I decide to play dumb, and just carry on walking. I figure I’ll pretend for as long as possible that I’m simple, or don’t speak English. My hotel is in sight by this point.
“Okay,” I say, confused look on my face, after he finishes his story.
“So you give us money?” he says.
“Okay,” I say, not giving him money.
“You give us money now.” he’s not asking this time.
“Okay,” I say. Walking a bit faster.
This goes on for two blocks. As dumb luck would have it, by the time he starts to loses his patience we’ve already reached my hotel.
Of course, at 4am, my two-star dive has its doors locked, and I have to ring the buzzer to get in.
Normally, the young girl on the desk buzzes me through two seconds later. Of course, normally I don’t show up in the dead of night accompanied by two burly Colombian guys yelling about drug money.
So she understandably doesn’t want to let me in.
Trying to buy time, and unsure whether this is a violent scam or a genuine case of mistaken identity, I tell the guy he can have his money in the morning. Just drop by, pick it up, no worries.
I buzz again, but she still doesn’t want to let me in.
“You give me money now.”
I usually carry a bunch of small-denomination bills in my pocket when I’m on unfamiliar turf, for precisely this kind of scenario, so I grab a wad of notes and stuff them into his hand.
“Okay, here’s your money.”
Buzz again. Still no response.
I’m trying not to notice that the money I’ve just given him amounts to about two US dollars, but he clearly has noticed and is quite angry.
I’m told I now owe him 57,000 pesos, which strikes me as unusually specific.
Fortunately, I never get to find out why he settled on that amount. The girl buzzes me through and, after a brief struggle, Scarface eats door.
End of anecdote.
To me, it sounds like a mugging. Drug guys threatened to beat me up and I gave them $2 – that fits the definition, right? It may be the lamest mugging in Colombian history, but it’s still a mugging.
Anyway, that’s my story and I’m sticking to it.
Next time, I’ll try to get stabbed or something.

“Beware of Hookers”, ICANN attendees told

ICANN has published a security guide for delegates planning to attend its meeting in Cartagena, Colombia, this December, which makes quite entertaining reading.
A highlight of the report (pdf), prepared by outside consultants Control Risks, warns attendees to steer clear of bar prostitutes who plan to take advantage of them.

All travelers should avoid bars which have public touts (or “spruikers”) standing outside encouraging them to enter. Many of these bars attract high levels of local prostitutes, some who intend to rob tourists by drugging them in the bar or in their hotel rooms.

Sage advice.
The report also recommends staying off the streets after 11pm, using official taxis, keeping your wallets clean of identifying information, and not resisting muggers/abductors.

Fight for your life, but not your possessions.

I’m cherry-picking the scary stuff here, obviously. In general, the report says Cartagena is fairly safe. Last year, there were only two kidnappings in the city.

Cartagena enjoys a mostly deserved reputation as one of the safe destinations for foreign travelers in Colombia. Certainly, violent crime rarely affects foreign visitors to the city.

ICANN has said that it will commission such reports when there is a concern that security at its chosen meeting locations may not be up to scratch.
I believe the new meetings security plan was introduced in response to the vague terrorism threats that clouded the Nairobi meeting earlier this year, keeping many flighty Americans at home.

.SO Registry copies .co launch policies

Somalia’s .SO Registry, which hopes to mimic a little of the success of .co when it starts accepting registrations in November, has adopted virtually identical launch policies.
The registry’s policy document (pdf), which appeared on its web site last week, does in fact appear to copy large chunks of text wholesale from .CO Internet’s equivalent paper (pdf).
(UPDATE: I’ve reason to believe this is because both documents share an author/editor)
For this reason, you can pretty much expect the same policies regarding the sunrise, landrush and general availability phases of the launch, which kicks off November 1.
It also means that .so domain names will be subject to the UDRP. The registry has evidently partnered with WIPO to administer these proceedings.
There are some differences between .co and .so, however.
Notably, .SO Registry has added a policy of allowing sunrise registrations for trademark typos, provided that the typo under another TLD has been won at UDRP or in court.
This basically appears to open the doors for any company that has won a .com domain in a UDRP case to register the equivalent .so, no matter how lunatic the UDRP decision was.
This is how the document describes the exception to the trademarks-only rule:

the Domain Name must be identical to a domain name which has been recovered by the Applicant or its authorized licensee in the context of a court, UDRP or other alternative dispute resolution procedure relating to that domain name in another top-level domain.

It’s followed by a comment, one of several apparently made by one of the document’s editors, that probably shouldn’t have been published on a public web site:

Comment Bart: we need to look at the allocation model here (rather hypothetical, but you never know): will they also go into auction if there are two applicants for the same domain name: one having the identical mark, and the other having the variant?)

Other differences include the fact that, unlike their Columbian counterparts, Somalians do not appear to get any special privileges, such as grandfathering or a priority sunrise phase.
There also does not to be a provision for a Specially Protected Marks list like the one .CO Internet used.
The registry’s policies will be governed by the laws of Japan, rather than Somalia (which, let’s face it, doesn’t have much in the way of a functional legal infrastructure).
.SO’s back-end is being handled by GMO Registry, the Japanese company that plans to apply for .shop and is working with Canon on its proposed .canon application.
I’ve previously reported on the roll-out time-line and pricing for the .so domain, here.

Yes, .co domains are subject to the UDRP

I’ve been getting a fair bit of search traffic over the last few days from people evidently wondering whether .co domain names are subject to the same UDRP rules as .com, so I thought I’d answer the question directly.
Yes, they are.
For avoidance of doubt, I’ve just talked to .CO Internet’s director of marketing, Lori Anne Wardi, who had just talked to the registry’s policy people.
She told me that .co domains are subject to the exact same ICANN UDRP as .com.
If you’re a .co registrant, you’re bound to the policy the same as you are in .com. If you’re a trademark holder, you file a complaint in the same way.
The only difference at the moment is that .CO Internet has contracted with only one UDRP provider, WIPO, but Wardi said that more providers may be signed up in future.

The .CO launch, by the numbers

The .co top-level domain is now live and open for general registrations, following a well-planned and self-evidently successful launch period.
The TLD is the country-code for Colombia, but it’s being sold as a generic alternative to .com by .CO Internet.
Here’s the story of the launch, explained with numbers:

27,000 – approximate number of active .com.co registrations made before the start of 2010, under the previous, much more restrictive regime (source).
5,000 – roughly how many of these .com.co registrants chose to participate in sunrise grandfathering, which would allow them to grab the equivalent .co domain before anybody else (source).
100 – number of brands on .CO Internet’s Specially Protected Marks List. These 100 companies, selected by Deloitte, had their brands placed on a registry-reserved list during the launch period.
83 – brands on the SPML who had chosen to register their .co names by the time the sunrise closed (source). Companies on the SPML who continue to decline their domain will see their brand released back into the pool.
10 – registrars initially approved to take .co registrations. Many more companies are selling the domains, but they’re all acting as resellers for these 10. More registrars will be approved in future.
225 to 335 – price in US dollars of a sunrise registration for trademark holders (source).
11,000 – approximate number of sunrise registrations
1,500 – approximate number of rejected sunrise applications (source)
27,905 – applications made during the landrush (source)
451 – landrush applicants applying for 10 or more domains
2,523 – domains receiving more than one landrush application. These domains will now be offered at auction. (source)
133 – number of countries where landrush applicants resided
350– Fortune 500 companies that have registered their trademarks under .co as of today
81,000 – the price in US dollars of the first .co domain to be auctioned, the single-letter e.co. The domain sold on Sedo to Bookmarks.com on June 10 (source)
350,000 – price in US dollars of the biggest seller to date, the single-letter o.co. The domain was sold to Overstock.com, directly by the registry, earlier this week. (source)
91,613 – registrations in the first 12 minutes of general availability, which started at 6pm UTC yesterday. (source)
216,159 – currently active registrations as of 10am UTC today, 16 hours into general availability (source)
? – number of .co domains still active July 22, 2011.

Have I missed anything? Let me know in the comments and I’ll add your data to the list.

Twitter registers t.co for URL shortener

Twitter has registered the domain name t.co, to use as a secure URL shortener.
Just minutes ago, t.co started resolving to a page containing this text:

Twitter uses the t.co domain as part of a service to protect users from harmful activity, to provide value for the developer ecosystem, and as a quality signal for surfacing relevant, interesting tweets.

The page links to a FAQ describing its current URL shortener, twt.tl.
Whois.co shows it’s registered as part of .CO Internet’s Founders’ Program, the scheme the Colombian registry put in place to plug its upcoming launch.
Under this program, companies can partner with .CO to get a free premium .co domain if they commit to promote it.
TechCrunch was previously the highest-profile site to join the program, when it registered disrupt.co.
I would say getting Twitter on board definitely beats that deal.
.CO Internet is also currently auctioning e.co for charity. Bids have already reached $24,000.
UPDATE: Twitter published a blog post on the launch. I guess they beat me by about three minutes.
“When this is rolled out more broadly to users this summer, all links shared on Twitter.com or third-party apps will be wrapped with a t.co URL,” the firm says.
Probably too soon to say for sure, but it looks like Bit.ly is kinda screwed.