.CO to accredit 20 more registrars

.CO Internet is looking for more registrars to start selling .co domain names.
The company has just released a request for proposals, saying it plans to accredit up to 20 new registrars over the next 12 months.
.CO’s registrar channel was limited by its agreement with the Colombian government to 10 registrars in its first year of business – the government had originally wanted only three, to limit gaming – but that restriction no longer applies.
While there are only 10 .co registrars currently, a few of them operate reseller channels or gateways that have enabled unaccredited registrars to also sell the domains, albeit on non-optimal terms.
According to the RFP, .CO is particularly interested in registrars that are willing to promote the .co TLD by either bringing it to new markets or making it the subject of special marketing campaigns.
While .co operates outside of ICANN control, the company is sticking to its policy of only accepting ICANN-accredited registrars into its channel.
Also, only registrars that are already accredited to sell .biz domains (as well as .com and .net) will be able to offer .co, presumably due to the fact that Neustar is the registry provider for both.
This effectively excludes about 115 registrars, many of which are shell or legacy accreditations used for drop-catching.
There are certain unspecified “special considerations” that apply to corporate-focused registrars, according to the RFP, presumably because they tend to be rather low-volume and generally focused on defensive registrations.

Aussies to back city TLD bids

Australian authorities are planning to back bids for .melbourne and .sydney top-level domains, according to a report in The Australian.
The article quotes an official from the New South Wales Premier’s Office saying there’s a plan to release a tender for the right to operate .sydney, and somebody from the City of Melbourne saying they’re “actively considering” .melbourne.
The report does not spell out the expected uses of the TLDs. I expect some of the strategy will depend on what business plans the successful registry operator comes up with.
The current draft of ICANN’s Applicant Guidebook protects city names, demanding applicants show proof of support or non-objection from the relevant public authorities.
The only exception is when the applied-for string matches a non-capital city name, but is not intended to represent that city.
That’s designed to allow brand or generic TLDs that match smaller place names — think .phoenix or .buffalo.
With the latest revision of the Guidebook, it is noted that it is up for national governments to decide what the appropriate entity to support a city TLD bid is, which could complicate matters,
There’s already a Facebook group devoted to a .melbourne application.

Registries could become registrars by summer

The big incumbent top-level domain registry operators could apply to also become registrars as early as June this year, according to a just-passed ICANN resolution.
Last November, ICANN decided to dump its longstanding policy of generally not allowing TLD registries to also own and operate registrars.
While the rule was designed primarily for TLDs won under the new gTLD program, it will also retroactively apply to operators of existing gTLDs.
Neustar (.biz) has already publicly stated its intention to vertically integrate, and is keen for ICANN to lift its current 15% registrar ownership restriction before the new gTLD program kicks off.
According to a resolution passed by ICANN’s board of directors on Thursday, Neustar is not the only registry operator to make such a request.
The board last week…

RESOLVED (2011.04.21.13), the Board directs the CEO to develop a process for existing gTLD registry operators to transition to the new form of Registry Agreement or to request amendments to their registry agreements to remove the cross-ownership restrictions. This process would be available to existing operators upon Board approval of the new gTLD Program.

ICANN currently plans to approve the gTLD program June 20 at its meeting in Singapore.
That gives CEO Rod Beckstrom and his team just two months to come up with a process for allowing the likes of VeriSign, Neustar and Afilias to either amend their contracts or move to the standard contract outlined in the new TLD program’s Applicant Guidebook.
I see a potential source of tension here.
The registry agreement template in the Guidebook has been described by some as an “adhesion contract” due to its heavy balance in ICANN’s favor.
Existing registries will very likely prefer to simply delete the cross-ownership restrictions in their current contracts and incorporate the new proposed Code of Conduct rules.
On the other hand, some have suggested that registries should be obliged to adopt the new Guidebook agreement in full, rather than amend their existing deals, in the interests of equitable treatment.
Registrars still signed up to ICANN’s 2001 Registrar Accreditation Agreement only get the option to upgrade wholesale to the 2009 agreement, it has been noted.

Three more countries get IDNs

Citizens of Algeria, Morocco and Serbia will soon be able to use domain names in their local Arabic and Cyrillic-based languages, after ICANN approved internationalized domain names for the three nations.
The three new ccTLDs are الجزائر (meaning “Al Jazair” for Algeria), المغرب (“al-Maghrib”, for Morocco) and .срб (“srb” for Serbia).
ICANN’s board approved the requests at a meeting on Thursday. They could enter the domain name system’s root in as little as 10 days, though delegations usually take longer.
There are now 37 IDN ccTLDs in IANA’s database of top-level domains, covering 27 countries.
On Thursday, ICANN also approved the redelegation of North Korea’s ASCII ccTLD, .kp, to an entity called Star Joint Venture Company.

Registry avoids .jobs shut-down

Employ Media has come to a deal with ICANN to avoid having its .jobs registry contract revoked, at least for the next few weeks.
Following discussions with ICANN’s lawyers, the company plans to amend its Charter, and has agreed to stop allocating non-company-name .jobs domain names until May 6.
ICANN threatened to terminate the .jobs registry deal in February, after Employ Media started allocating thousands of premium vocational and geographic domains to a partner, the DirectEmployers Association, to act as entry points for Universe.jobs.
In a breach notice (pdf), ICANN said that this use of .jobs domains “is inconsistent with the purpose stated in the .JOBS Charter and represented to the ICANN community”.
The .JOBS Charter ostensibly restricts registrations to human resources professionals, but in practice there’s a great big loophole that allows anybody to cheaply qualify for a domain.
In February, ICANN general counsel John Jeffrey told Employ Media:

By not establishing any meaningful restrictions on who may register second level registrations in the .JOBS TLD, Employ Media put in operation a TLD where anyone can register names, thus defeating the purpose for which the sponsored TLD came into existence.

In its response, the registry noted that it had followed ICANN’s proper procedures for introducing new “registry services”, such as the Phase Allocation Plan that allowed it to seed Universe.jobs.
It accused ICANN of bending to the wishes of the .JOBS Charter Compliance Coalition, a group of independent jobs sites operators that had objected to Universe.jobs.
Employ Media’s chief executive Brian Johnson wrote:

This is a sad day for both the Internet community and the international human resource management community. ICANN should be promoting competition and working cooperatively with its contractual parties, but instead is choosing to ignore the plain meaning of its contract with Employ Media in order to appease some apparently well‐financed and well‐connected provocateurs.

Since that letter (pdf) was sent, ICANN and the registry have been engaged in private discussions aimed at resolving the conflict, as allowed by the registry agreement.
In the latest set of correspondence, exchanged over the last week, it has emerged that ICANN has agreed to give Employ Media time to remedy the situation by amending its Charter.
The letters do not reveal whether the amendments will allow Employ Media to continue to offer Universe.jobs or not. I suspect they will.
The amendments may require the company to consult with its nominal sponsor, the Society for Human Resource Management.
ICANN wants a proposed Charter amendment on its desk by May 2. It has agreed to take no further action related to the breach of contract allegations until May 6.

New TLDs timetable tightened

ICANN’s effort to squeeze out a process for approving new top-level domains has been about as easy and painless as giving birth, so it perhaps appropriate that it now expects to take at least nine months to gestate the very easiest applications.
The new version of the Applicant Guidebook, published Saturday, makes a number of changes to the expected new TLDs timetable, including the addition of an extra month to the minimum likely processing time for non-controversial strings.
This is not, as you might think, a result of the new objection powers granted to the Governmental Advisory Committee.
(UPDATE: On closer analysis, it appears that the timetable has in fact been rejiggered in order to give more time to the GAC’s Early Warning mechanism. Thanks to Mike, in the comments, for the correction.)
The Administrative Check part – the bit where ICANN goes through the applications to make sure they’ve all been correctly filed – that has been extended, from four weeks to eight.
ICANN has also shortened the first-round application-filing window by a month, to 60 days, off-setting the extended processing time.
New TLDs may start entering the root around the same time they were previously expected.
The timetable for the launch of new TLDs now looks a little like this:
June 20 – Applicant Guidebook approved in Singapore.
July-October 2011 – four-month communication/outreach period.
November-December 2011 – first-round application window
October 2012 – first new TLDs delegated to DNS root.
The new Guidebook advises applicants to avoid waiting to the last minute to file their applications, due to the complexity of the new TLD Application System (TAS) it’s created.
Given the application period is likely to end shortly after the end of year holiday period, I expect applicants will have plenty of impetus to get their applications in early without encouragement.

ICANN brings “loser pays” to domain disputes

ICANN has significantly strengthened brand-owner protections in new top-level domains by proposing, amongst other things, a new “loser pays” model for some cybersquatting disputes.
The Uniform Rapid Suspension process, which is designed to give trademark owners a quick, cheap way to take down obvious examples of cybersquatting, may now occasionally carry a response fee.
According to ICANN’s newly revised Applicant Guidebook, which was published early this morning:

A limited “loser pays” model has been adopted for the URS. Complaints listing twenty-six (26) or more disputed domain names will be subject to an Response Fee which will be refundable to the prevailing party. Under no circumstances shall the Response Fee exceed the fee charged to the Complainant.

In other words, if a somebody registers more than 25 domains that appear to infringe upon the trademarks of a single company, they will have to pay a few hundred dollars, refundable, if they want to defend their case. Judging from UDRP history, this will likely apply to very few people.
The number 25 comes from the May 2009 report of ICANN’s Implementation Recommendation Team, which devised many of the new gTLD program’s rights protection mechanisms.
This change is one of several made in the new Guidebook, addressing concerns raised by the Governmental Advisory Committee, which had consulted closely with the IP lobby.
The GAC didn’t get everything it wanted, however. It had asked for repeat cybersquatters to lose their right to respond under the URS, but ICANN declined, citing the need for due process.
But the Guidebook does now also require new TLD registry operators to offer two types of rights protection mechanism during their launch phase, as the GAC had requested.
Whereas earlier drafts mandated either a Trademark Claims service or a Sunrise period, now registries will have no choice: they have to offer both at a minimum.
The Trademark Claims services notifies registrants if they try to register a domain name that matches a trademark registered in a central Trademark Clearinghouse.
The registrant will have to certify that they’re not infringing any rights before they get the domain. If they do register it, the affected trademark holder will receive a notification that the domain has been registered and can choose to take action such as filing a URS claim.
The idea behind the service is to deter cybersquatters, possibly reducing brand owners’ costs from having to defensively register their names in all new TLDs.
The Sunrise period, which is now also mandatory, is not entirely dissimilar to the sunrise periods we’ve come to expect from new TLD launches over recent years.
The new Guidebook states that the Trademark Claims service must be offered for at least 60 days after a new TLD enters general availability and the Sunrise must be at least 30 days before.
The fact that both services are now mandatory has helped ICANN address the thorny question of what should constitute a valid trademark.
Earlier drafts of the Guidebook required trademarks to have been subject to “substantive review” – a check by a national authority that the trademark is for real and in use.
The worry was that speculators could game the system by picking up large numbers of trademarks in countries that give them away like candy. It’s happened before.
But the review requirement was criticized by the GAC and others as it excluded trademarks in much of the world outside of the US.
In response to these criticisms, ICANN has removed the reference to substantive review. Instead, the yet-to-be-decided manager of the Trademark Clearinghouse will be given the task of validating that each trademark submitted is legit.
Companies need only submit a declaration and a single piece of evidence of use in order to get into the Clearinghouse, thus enabling them to partake of the Sunrise.
No such validation will be required in order to participate in the Trademark Claims service, though brand owners will need to be listed in the Clearinghouse for both mechanisms.
Evidence of use will also be needed to file URS complaints, but that can be done separately at the time of filing, with no need for a Clearinghouse registration.
ICANN chairman Peter Dengate Thrush, himself an IP lawyer, once stated, possibly in jest, that no matter what you do, you can be certain that IP lawyers will demand more protections.
Whether the rights protections mechanisms included in the Guidebook are now sufficient to calm trademark interests’ nerves remains to be seen.

ICANN gives governments powers over new TLDs

ICANN has made some significant concessions to government demands in the newly published revision of its new top-level domains Applicant Guidebook.
After lengthy consultations with its Governmental Advisory Committee over the last few months, ICANN has updated the rulebook to address the vast majority of GAC concerns.
We’ve gone from the “proposed final Applicant Guidebook” published in November to the “April 2011 Discussion Draft” that appeared on the ICANN web site in the wee hours of this morning.
On first perusal, it appears that ICANN has walked the fine lines between GAC advice, hard-fought community consensus and common sense more or less successfully.
While the new Guidebook gives plenty of ground to the GAC, making it a more integral part of the new TLDs approval process, it avoids adopting some of its more problematic requests.
In this post, I’ll look at the powers ICANN has given to governments to object to TLDs.
Early Warning System
While ICANN has sensibly not given individual governments the right to veto TLDs they are not happy with, they do get substantially more input into the approval process than in previous drafts.
The major update to the Guidebook is a new Early Warning system that will allow governments to pre-object to TLDs they don’t like.
An Early Warning, which can only be filed by the GAC chair, is “an indication that the application is seen as potentially problematic by one or more governments.”
Applicants in receipt of such a warning will have 21 days to decide whether to drop out of the process, receiving a $148,000 refund, 80% of their $185,000 application fee.
But they won’t have to. The warning is just a heads-up that the GAC or some of its members may formally object at a later stage. A warning does not represent a GAC consensus position.
The Early Warning process will run for 60 days, at the same time as the public comment period that begins the day the applications are published.
Advice of Doom
Any applicants that decide to ignore such a warning face the possibility of receiving a formal GAC objection, which could come at any point in the first seven months after the applications are published.
This is now being called “GAC Advice on New gTLDs”. It could be quite a powerful tool:

GAC Advice on New gTLDs that includes a consensus statement from the GAC that an application should not proceed as submitted, and that includes a thorough explanation of the public policy basis for such advice, will create a strong presumption for the Board that the application should not be approved.

This is pretty close to a GAC veto, but it crucially requires GAC consensus. The Guidebook explains:

GAC Advice on New gTLDs should identify objecting countries, the public policy basis for the objection, and the process by which consensus was reached.

Even if the GAC reaches consensus, the ICANN board will be able to overrule its objections in accordance with its bylaws, in much the same way it just did with .xxx (in practice, I suspect .xxx may ultimately prove a fairly unique exception to the rule).
The Guidebook indicates that any wishy-washy, non-consensus, politician-speak advice given by the GAC will not be considered grounds for rejecting an application. The objection must be specific, grounded, and it must have support.
Importantly, ICANN has not conceded to the GAC’s request to allow applicants to amend their applications to remedy the GAC’s concerns.
As I noted earlier in the week, this could have led to companies gaming the system, and ICANN has ruled out amendments for precisely that reason.
Freebies
Individual governments will of course be allowed to object to any application using any of the other procedures that the Guidebook allows, such as the Community Objection.
ICANN’s problem is that these processes carry third-party fees, and governments don’t think they should have to pay these fees (for some reason that’s never been adequately explained).
Addressing this concern, the new Guidebook says that ICANN will cover each national government to the tune of $50,000 to fund a single objection.
That’s a total of potentially well over $1 million, funded from ICANN’s reserves. ICANN expects that governments will coordinate their objections to limit its costs.
Overall, it appears that ICANN has addressed pretty much everything the GAC wanted in terms of objections procedures. With a couple of reasonable exceptions, the GAC has received what it asked for.
Members may not be completely happy with ICANN’s decrees on what form GAC advice must take in order to have a useful impact, but in general it seems that this could well now be a closed issue.
In my next post, I’ll look at how intellectual property protection changes in the new Guidebook.

.xxx domains go live

Click here: icmregistry.xxx, then come back.
That’s right. After ICM Registry’s almost 11 years of campaigning, and almost $20 million in legal and other expenses, .xxx domain names are actually live in the domain name system.
ICANN, IANA, the US government and VeriSign, in that order, have all agreed to delegate the internet’s newest gTLD, and the first few .xxx domains went live within the last couple hours.
The domains sex.xxx and porn.xxx are now also resolving to placeholder sites. They’re currently “safe for work”, but possibly not for much longer.
IANA has a .xxx page, complete with a lengthy delegation report (in a snazzy new pdf format) that broadly explains the convoluted process ICANN used to ultimately, albeit reluctantly, approve the TLD.

North Korean domain to change hands

ICANN is set to redelegate .kp, the country-code top-level domain for North Korea, when its board of directors meets next week.
It’s less than four years since .kp was first created. In September 2007, IANA delegated the ccTLD for the first time to the Korea Computer Center, a Pyongyang-backed governmental organization.
The technical side of the registry is currently handled by KCC Europe, a German company, but while some .kp domains still resolve, the official registry web site has been offline for months.
The redelegation is part of the ICANN board’s consent agenda. This means that, barring surprises, it will simply be rubber-stamped with no substantive discussion.
Because ccTLD redelegations are handled in private, we won’t know who the new registry manager is until after the handover happens and the IANA report is published.
In other ccTLD news, ICANN may also create three new internationalized domain name ccTLDs, for Serbia (.срб ), Algeria (الجزائر) and Morroco (المغرب).
Those delegations are part of the board’s regular agenda for its April 21 meeting, and will be discussed.