Three-million-domain .au deal up for grabs

auDA has formally launched the process that will could see it replace .au back-end provider Neustar with an in-house registry by the end of June 2018.
The Australian ccTLD operator has opened a “Request for Expressions of Interest” as the first stage of a procurement process for software and/or services to support its recently announced Registry Transformation Project.
It’s looking for companies that can provide all the major pieces of a domain name registry — EPP registry, Whois, DNS, etc — and my reading of the REOI reveals a preference towards a system owned and operated by auDA.

Respondents can respond with products, technology and / or services for all or part of the elements of the Registry Transformation Project, and are free to partner with other respondents to put together combined proposals.
auDA intends to establish a dedicated .au registry, and have all arrangements in place to support this, by 30 June 2018.

The organization even talks about eventually becoming one of ICANN’s approved Emergency Back-End Registry Operators.
.au has grown to over 3 million domains over the 15 years it was being managed by AusRegistry, which was acquired by US-based Neustar in 2015. This deal is due to expire next year.
So it’s a big contract, and one that is likely to attract a lot of interest from players big and small.
That said, registry solutions are typically offered very much on a service basis. The market for licensed registry software is not exactly bustling, and auDA also requires source code access as a condition of any deal.
auDA said the deadline for responses to the REOI is June 26. It will decide upon its next steps, which could be a formal request for proposals, in the last week of July.
Further details can be found here.

.CO Internet looking for more registrars

.CO Internet is expanding its registrar channel with a new Request For Proposals.
The company wants would-be registrars to respond with the commitments they’re willing to make to market and promote .co domains, particularly in markets where .co is not currently popular.
Only ICANN-accredited registrars need apply.
Amusingly, registrars also need to be specifically accredited to sell .biz domains. Presumably this is due to .CO’s relationship with back-end provider Neustar, which also runs .biz.
The company has about 30 registrars right now, but many of those operate very large reseller networks, so there’s no shortage of places to buy a .co if you want one.
.CO deliberately kept its registrar numbers low — only 10 at launch — in order to cut down on abuse and to keep a tighter leash on gaming during the 2010 landrush process.
The RFP can be found here.

.eu registry contract up for grabs

The European Commission has opened up the .eu registry contract to competitive bidding.
The sort-of ccTLD has been managed by EurID since it launched 2004 but its contract, which has already been extended to its maximum term, is due to expire in October next year.
Would-be usurpers must be not-for-profit organizations based in the European Union, according to a Commission RFP, which should narrow the field quite a lot.
The .eu space has 3.7 million registered domain names, growing at 5.4% a year. Considering that the TLD is open to all in the EU, the numbers fare poorly compared to many European ccTLDs.
The deadline for submissions is June 20.

ICANN issues new gTLD dispute RFPs

ICANN has issued two requests for proposals for providers to administer dispute resolution services for the new gTLD program.
It’s looking for outfits to manage the Registry Restrictions Dispute Resolution Procedure (RRDRP) and Trademark Post-Delegation Dispute Resolution Procedure (Trademark PDDRP).
The former is for people who think a Community gTLD registry is mishandling its registration restrictions, the latter for trademark owners who believe a registry is turning a blind eye to cybersquatting.
ICANN has a requirement that the respondents to the RFPs must have experience with dispute resolution, so expect the usual suspects (ie UDRP providers) to wind up on the shortlist.

ICANN looking for new gTLD testing provider on very tight deadline

ICANN is seeking one or more pre-delegation testing providers for its new gTLD program on a very ambitious timetable.
An RFP issued yesterday calls for a company that can scratch-build a testing suite to put new gTLD applicants through the ringer before they go live, and have it up and running by March 25, 2013.
Pre-delegation testing is the last stage of the new gTLD program’s approval process.
Some new gTLD applicants have recently called on ICANN to begin testing as soon as possible — before even Initial Evaluation has finished — in order to speed up time to market.
The Applicant Guidebook suggests that ICANN itself would be doing the testing, and some applicants had made that assumption, but that’s clearly not the case.
The RFP spells out exactly what is required of the testing providers.
First, they’re expected to build bespoke software to run the tests.
In addition to load-testing and verifying the registry’s compliance with standards such as EPP, DNSSEC and Whois, it also needs a custom-made user interface for applicants and back-end integration with ICANN’s wobbly TLD Application System.
ICANN also wants to be able to open-source the software, which seems to rule out any off-the-shelf testing suites.
RFP respondents also need to be able test 20 applicants’ back-ends per week — potentially scaling up to 100 per week — as soon as ICANN starts signing registry agreements next year.
ICANN does not expect to announce the winning provider(s) until December 5. The deadline for responses is November 20.
In short, it looks like a challenging project on a very tight deadline.
I wonder how much institutional knowledge there is out there of, say, DNSSEC, in companies that are not also involved in new gTLD applications as either applicant or back-end.
The pool of possible RFP respondents is likely very small indeed.
The ability to run tests on the testing suite itself may also be limited by the timetable and the possible shortage of guinea-pig registry back-ends.
Why ICANN has waited until this very late date to issue the RFP is a real head-scratcher.
ICANN is offering a 24-month contract with a possible 12-month extension. The RFP can be downloaded here.

ICANN to issue update on IANA contract

This weekend’s shock news that ICANN’s bid to renew its IANA contract with the US government failed is still without an official, detailed explanation, but ICANN may soon reveal more specifics.
The National Telecommunications and Information Administration said Saturday that no bidder for the IANA contract had met its requirements, and that it was canceling the RFP until a later date.
It extended ICANN’s management of IANA for another six months.
CEO Rod Beckstrom said at a press conference here at the public meeting in Costa Rica today that ICANN cannot comment on the reasons its bid was rejected for now.
However, it’s going to meet with the NTIA soon to discuss the matter and may issue an update later.
“We were invited to have a debriefing with them to learn more about this,” Beckstrom said. “Following that discussion we will share any information we are allowed to share.”
Here in San Jose, there are several theories floating around the show floor.
The first hypothesis, which was popular on Saturday but which since seems to have fallen out of favor, is that it was a deliberate attempt to, in the words of one attendee, “fuck with” Beckstrom.
His contract expires in early July, and it was speculated that the NTIA would prefer to deal with his successor on the IANA contract, forcing him to leave the organization on a bum note.
I don’t really buy that. I can’t see the NTIA playing personality politics to that extent, not with the future of internet governance on the line.
The other theory doing the rounds is that ICANN fell foul of some rather esoteric US procurement guidelines – that the NTIA was legally unable to approve its bid.
Others speculate that ICANN just submitted a really crappy response to the RFP, or a response that failed to take the NTIA’s requirements seriously enough.
This seems more likely.
Whatever the reason, the way the news broke – apparently catching ICANN off-guard as much as anybody else – certainly suggests that the NTIA either screwed up its communications or that it wanted to make one of its trademark pre-show sabre-rattling statements.

London issues .london RFP through Olympic bid system

London & Partners, the official promotional agency for London, has released a request for proposals for a registry to apply for and run .london as a new top-level domain.
Bidders will have to sign up for CompeteFor, an online procurement tool designed primarily for the London 2012 Olympics, in order to submit their proposals.
UK-based registries Nominet and CentralNic have already said they plan to respond to the RFP, but L&P says that it is open to companies anywhere, not only in the UK and EU.
The RFP is open until January 5 at noon GMT.

Aussies to apply for four geo-TLDs

The Australian state governments of New South Wales and Victoria have put out a tender for a registry provider for up to four new top-level domains.
They want to apply to ICANN next year for geographic gTLDs including .victoria, .sydney, .melbourne and possibly .nsw, according to the RFP.
The new gTLDs would be self-funded commercial ventures, with some names reserved for public use, it says. Revenue would be shared between the government and the operator.
If a local presence is taken into account then ARI Registry Services, which recently changed its name from AusRegistry International to dilute the perception that it was too Australia-focused, could be considered a likely front-runner for the gigs.
The tender closes November 15.

Corsica seeks new gTLD registry operator

The local government of the French island of Corsica is looking for contractors to apply for and manage a .corsica top-level domain.
The Executive Council of the Collectivité Territoriale de Corse issued an RFP in late September. The deadline for responses is October 17, a week from now.
The desired string appears to be the Anglicized .corsica, rather than the French .corse.
Corsica, situated in the Mediterranean, is one of France’s 22 official regions. According to Wikipedia, it has slightly more political power than its mainland counterparts.
Under ICANN’s new gTLD application rules, geographical strings need the approval of the relevant local government before they can be accepted.
I expect any .corsica application would need a letter of support or non-objection from the French national government as well as the Corsican executive, before it is approved.
(via Jean Guillon)