DotFree starts taking .free domain preregistrations

The DotFree Group, which plans to apply to ICANN to run .free as a top-level domain, has become one of the first would-be registries to open its doors for preregistrations.
From noon UTC today, the Czech company has made a tool available on its web site enabling users to reserve their desired strings by handing over their contact information.
Of course, there’s no guarantee any preregistration will actually turn into a .free domain – ICANN may turn down DotFree’s application or award the string to another bidder.
While the plan is to offer some .free domains free of charge, DotFree intends to hold tens (or hundreds) of thousands of “premium” strings for auction or paid-for registrations.
In other words, if you try to register any really juicy strings today, you’re out of luck.
DotFree is one of only a few unapproved TLD registries to accept preregistrations.
ICM Registry started taking .xxx preregs a few years ago, but only after it had already received ICANN’s approval (which was, of course, later revoked).
Another wannabe TLD operator, the MLS Domains Association, is charging “multiple listing service” real estate brokers many hundreds of dollars for the opportunity to own their own .mls domain name.
UPDATE: Messing around with the preregistration tool, I’ve noticed that it appears to ban any string that ends with the number 4. Presumably these will be “premium”, due to the “for” pun.

.XXX debate could test GAC powers

The long-running .xxx top-level domain saga has tested ICANN processes to their limits over the last decade, and it looks like it may do so at least one more time.
Digging a little deeper into the board’s decision to consult with its Governmental Advisory Committee before approving the TLD, it looks like the discussion will be quite broad-based.
The .xxx consultation could in fact have consequences for the board/GAC power balance, helping define the parameters of their future interactions.
This PDF, published at the same time as last week’s board resolution on .xxx, outlines three GAC positions that could have a bearing on the matter.
The first is its communiqué from the Wellington meeting in 2007, which noted that several GAC members were “emphatically opposed” to the introduction of .xxx.
The GAC operates on a consensus basis. When it can’t find consensus, its communiqués also reflect minority positions. So ICANN now wants to know whether the Wellington letter constitutes GAC “advice”.

The question remains whether a position taken by “several members of the GAC” can be equated with GAC advice on public policy matters. If it is not GAC advice, then the concern of inconsistency [of the .xxx contract with GAC advice] diminishes.

Some may be surprised to discover that, after over a decade, there’s no broad agreement about when something the GAC says constitutes official “advice” that ICANN, under its bylaws, must consider.
Attendees to the Brussels meeting this June will recall that the joint board-GAC meeting, transcribed here, spent most of its time labouring on this apparent oversight.
In consulting with the GAC on .xxx, there’s an outside chance that some answers with regards the definition of “advice” may be found.
It wouldn’t be the first time ICM Registry’s controversial application has forced ICANN to address shortcomings in its own accountability procedures.
Notably, the Independent Review Process, promised in the bylaws for years, was eventually implemented to allow ICM’s appeal after it had pushed the Reconsideration Request process to its limit.
ICANN’s latest resolution on .xxx also refers to a letter (pdf) GAC chair Heather Dryden sent to the board in August, which expressed a desire that no “controversial” TLDs should be added to the root.
While ostensibly addressing future TLD applications, rather than TLDs applied for under previous rounds, the letter did say that “objection procedures should apply to all pending and future TLDs”, which was widely interpreted as referring directly to .xxx.
Last week’s ICANN board documents say:

If the “pending” TLD refers to .XXX, the approval of the .XXX sTLD Registry Agreement without allowing for these types of objections would be inconsistent with GAC advice.

I’ve reason to believe that the “pending” language may have been inserted quite late into the drafting of the Dryden letter, and may not enjoy the unanimous support of GAC members.
Regardless, the letter implies that whatever “morality and public order” or “Rec6” objections process winds up in the new TLD Applicant Guidebook should also apply, retroactively, to ICM.
If ICANN were to agree on this point, a precedent would presumably be set that would allow the GAC to issue thirteenth-hour “advice” that moves the goal-posts for future new TLD applicants, removing a significant amount of predictability from the process.
For that reason, I think it’s unlikely that ICM will be told it is subject to the Rec6 process (whatever that may ultimately look like).
The consultation, however, may result in some clarity around where the GAC’s powers of “advice” begin and end, which is probably a good thing.

Will .xxx be approved today?

Will the adults-only .xxx top-level domain be approved today, or will the hot potato be tossed to governments for a decision?
That’s the question facing ICANN’s board of directors, which is set to discuss the controversial TLD for the umpteenth time today.
The last resolution it passed on .xxx called for a public comment period, followed by a decision on whether the registry contract is compatible with old Governmental Advisory Committee advice.
With the comment period closed, it appears that all that remains is to decide whether a new GAC consultation is required before the contract can be approved or rejected.
Some opponents of .xxx are demanding a GAC consultation.
Diane Duke, director of porn trade group the Free Speech Coalition, wrote to ICANN this week, urging it to refer the application back to the GAC.
As Duke knows, many international governments are opposed to .xxx.
A week ago, Australia’s socially conservative, pro-censorship broadband minister, Stephen Conroy, also asked ICANN for another GAC consultation, expressing his “strong opposition” to the TLD due to its “lack of identified public benefit”.
And Conroy is surely not alone. There can be few governments that would be happy to be seen to endorse pornography, regardless of its legal status in their jurisdictions.
The GAC is firmly of the view that “controversial” TLDs present a risk to the global interoperability of the internet. The fear is that strings such as .xxx could lead to blocking at national borders and ultimately fragmentation of the DNS root.
Whichever decision ICANN makes today, it is sure to cause controversy one way or another.

ICANN rejects porn domain info request

ICANN has turned down a request from porn trade group the Free Speech Coalition for more information about the .xxx top-level domain application, including a list of its pre-registrations.
The organization sent a letter (pdf) to the FSC’s director Diane Duke last week, saying that the materials it requested about ICM Registry and IFFOR, its sponsorship body, are confidential.
This would make the information exempt from ICANN’s Documentary Information Disclosure Policy.
The FSC had specifically requested:

1. The list of the IFFOR Board members;
2. The list of proposed members of the Policy Council;
3. IFFOR’s Business Plan/Financials;
4. Business Plan/Financials Years 1‐5 utilizing 125,000 Initial Registrations;
5. The list of .XXX sTLD pre-registrants who have been identified to ICANN; and
6. ICM’s Proof of Sponsorship Community Support as submitted to ICANN.

According to ICANN, ICM was asked if it would like to lift the confidentiality restrictions and ICM did not respond.
The FSC believes that many of .xxx’s 180,000+ pre-registrations are defensive in nature, made by pornographers who would really prefer that the TLD is never approved, which ICM disputes.

Christians defeated? No comment on .xxx

ICANN’s latest public comment period on the .xxx top-level domain closes today with nary a Christian in sight.
The latest forum is the sixth that ICM Registry has had to endure since it first filed its TLD application, and most of them have been marked by voluminous outcries orchestrated by US-based religious groups.
Organizations such as the Family Research Council have been responsible for tens of thousands of form-letter comments over the years, but this time they’re nowhere to be seen.
Their efforts lobbying the Bush administration were credited by some with killing off the TLD by back-channels a few years ago.
So have they given up, changed tactics, or did somebody just miss a memo? Beats me.
In other .xxx news, today I’ve also reported on recent developments at ICM, including a plan to create several free-to-list directory sites on “super-premium” .xxx domains. To find out more, head over to The Register.

.xxx bigger than .asia

It has not and may never be delegated, but the .xxx top-level domain now has more pre-registrations than .asia, the last big gTLD launch, has live domains.
The ICM Registry web site currently counts 180,352 pre-regs. ICM tells me this number counts the unique strings that have been applied for, excluding duplicate applications.
By contrast, DotAsia’s two-year-old namespace had shrunk to 177,872 by the start of September, according to HosterStats.
ICM reported 110,000 pre-registrations at the time it re-entered contract talks with ICANN in late June; media coverage increased that to 162,000 within a couple of weeks.
The company has previously said that only 6,435 pre-regs were self-identified as defensive in nature, although this is disputed by its opponents at the Free Speech Coalition.

Pornographers rally to decry .xxx

The Free Speech Coalition has issued an official call to action to rally its members against the .xxx top-level domain application.
It’s been on the front page of the porn trade group’s web site since yesterday, but has been slow to take off judging by the number of responses filed with ICANN in the last 24 hours.
The FSC wants it members to write to ICANN to ask for the TLD to be rejected. It hits seven major points, but essentially just backs up what FSC chair Diane Duke told ICANN last week, which I reported on here.
There’s also a Zoomerang survey that industry members can take. It asks users to merely answer two questions in the affirmative:

I am a member of the online adult entertainment community and I oppose ICM’s application for a .XXX sTL
I have have defensively pre-registered .XXX domain names and I oppose .XXX

The idea is to show that many .xxx pre-registrations are made by people who would prefer that the TLD never sees the light of day.

.XXX registry goes on the counter-attack

ICM Registry has issued a strongly worded response to its critics at the Free Speech Coalition, questioning the porn trade group’s relevance.
As I blogged yesterday, the FSC has asked ICANN to release documents disclosing the level of support the .xxx domain, so it can more effectively argue against its approval.
ICM has responded with a letter to ICANN that paints the FSC as overly US-centric and says its arguments deal with issues that have long been resolved.

We understand that the FSC currently has approximately 1,000 members. We further understand that both its leadership and its members are almost exclusively U.S.-based.
…
The bottom line is that the FSC’s comments simply restate the arguments they have made in the past. Their claims were inaccurate, unsupportable, untimely, and irrelevant when first made, and remain so today.

The would-be registry claims that, contrary to the FSC’s claims, only a tiny portion of its 179,000 pre-registrations are defensive in nature, 6,435 in total.

Porn group tries to delay .xxx bid

The Free Speech Coalition has asked ICANN to prove that the .xxx top-level domain application has the level of support that ICM Registry claims it has.
The FSC, which represents thousands of porn webmasters, has filed a request under ICANN’s Documentary Information Disclosure Policy for a list of the people who have already pre-registered .xxx domains, among other items.
The organization wants to prove that .xxx has no support among the adult community, and that most of ICM’s 179,000 pre-registrations are made by domainers or are defensive, made by pornographers who really don’t want .xxx.
FSC president Diane Duke wrote to ICANN general counsel John Jeffrey (pdf):

The adult entertainment community – the community which would be most impacted by the introduction of a .xxx sTLD – requires more information about the application in order to provide the appropriate level of feedback to the ICANN Board for it to make an informed decision.

The FSC also wants ICANN to add another 30 days to the current public comment period after the disclosure is made, to give it a chance to respond properly to the new data.
This would, of course, add further delay to the .xxx application.
The FSC also wants to know more about IFFOR, the International Foundation For Online Responsibility, the policy body that would oversee .xxx.
Specifically, the DIDP request covers the names of IFFOR’s board of directors, policy council members, business plans and financial projections.
ICM is opposed to the request and will be officially responding shortly. Its president, Stuart Lawley, told me the information the FSC has requested is known to ICANN, but that it’s confidential.
He also said that the issue of community support is already closed; ICANN made that decision five years ago, a decision that was reinforced earlier this year by an Independent Review Panel.

What .xxx means for trademark holders

Trademark holders have been screwed over by ISP domain name wildcarding more than they realise, I’ve discovered from the .xxx contract documents.
ICM Registry is planning a novel approach to trademark protection if its application to launch the .xxx top-level domain is successful, but it’s been watered down compared to its original plan.
Hypothetically, let’s say you’re Lego. You really, really don’t want some cybersquatter snapping up lego.xxx and filling it with… well, you can imagine what Lego porn might look like.
At the same time, for the sake of your family-friendly brand, you don’t want to actually own a resolvable lego.xxx either.
And you certainly don’t want to be forced to to hand some pornographer over $60 a year for each of your brands. Some companies could see this as supporting pornography.
ICM had originally planned to allow companies in this position to pay a one-time fee to have their brand.xxx turned off permanently.
Personally, I like this idea. It would give the IP lobby a lot less to complain about in discussions surrounding the new TLD program.
But the company may now water down this plan, called IP Protect, due to the way that non-existent domains are increasingly handled by some ISPs.
As you probably know, ISPs worldwide are increasingly capturing NXDOMAIN traffic in order to show search results and advertising links to their customers.
It’s generally frowned upon in DNS circles, and it’s now likely to have the effect of making IP Protect costlier and more of an administrative hassle for brand owners.
You’re Lego again. You pay ICM the one-time shut-down fee, only to find that Comcast is now showing its users links to Lego porn whenever they type in lego.xxx.
ICM president Stuart Lawley tells me that one option currently being looked at is to have IP Protect domains resolve to a standard page at an ICM-controlled server.
The problem here is that ICM has to pay ICANN and its registry back-end provider annual fees for every resolving domain name, and that cost will have to be passed on to the registrant, in our case Lego.
Lawley says that ICM is “engaging” with the ICANN intellectual property community to figure out the best solution. It appears that both options are still open.