Latest news of the domain name industry

Recent Posts

US and EU call for Whois to stay alive

Kevin Murphy, January 31, 2018, Domain Policy

Government officials from both sides of the Atlantic have this week called on ICANN to preserve Whois as it currently is, in the face of incoming EU privacy law, at least for a select few users.
The European Commission wrote to ICANN to ask for a “pragmatic and workable solution” to the apparent conflict between the General Data Protection Regulation and the desire of some folks to continue to access Whois as usual.
Three commissioners said in a letter (pdf) that special consideration should be given to “public interests” including “ensuring cybersecurity and the stability of the internet, preventing and fighting crime, protecting intellectual property and copyright, or enforcing consumer protection measures”.
David Redl, the new head of the US National Telecommunications and Information Administration, echoed these concerns in a speech at the State of the Net conference in Washington DC on Monday.
Redl said that the “preservation of the Whois service” is one of NTIA’s top two priorities at the moment. The other priority is pressing for US interests in the International Telecommunications Union, he said.
Calling Whois “a cornerstone of trust and accountability for the Internet”, Redl said the service “can, and should, retain its essential character while complying with national privacy laws, including the GDPR.”
“It is in the interests of all Internet stakeholders that it does,” he said. “And for anyone here in the US who may be persuaded by arguments calling for drastic change, please know that the US government expects this information to continue to be made easily available through the Whois service.”
He directly referred to the ability of regular internet users to access Whois for consumer protection purposes in his speech.
The European Commission appears to be looking at a more restrictive approach, but it did offer some concrete suggestions as to how GDPR compliance might be achieved.
For example, the commissioners’ letter appears to give tacit approval to the idea of “gated” access to Whois, but called for access by law enforcement to be streamlined and centralized.
It also suggests throttling as a mechanism to reduce abuse of Whois data, and makes it clear that registrants should always be clearly informed how their personal data will be used.
The deadline for GDPR compliance is May this year. That’s when the ability of EU countries to start to levy fines against non-compliant companies, which could run into millions of euros, kicks in.
While ICANN has been criticized by registries and registrars for moving too slowly to give them clarity on how to be GDPR-compliant while also sticking to the Whois provisions of their contracts, its pace has been picking up recently.
Two weeks ago it called for comments on three possible Whois models that could be used from May.
That comment period ended on Monday, and ICANN is expected to publish the model upon which further discussions will be based today.

What next for new TLDs? Part 4 – GAC Concerns

Kevin Murphy, December 15, 2010, Domain Policy

Like or loathe the decision, ICANN’s new top-level domains program appears to have been delayed again.
But for how long? And what has to happen now before ICANN starts accepting applications?

In short, what the heck happened in Cartagena last week?
In this four-part post, I will attempt an analysis of the various things I think need to happen before the Applicant Guidebook (AGB) is approved.
In this fourth post, I will look at areas of the AGB that the Governmental Advisory Committee is still concerned about.
GAC Concerns
The GAC’s laundry list of objections and concerns has grown with every official Communique it has released during an ICANN public meeting over the last few years.
While it has not yet published its official “scorecard” of demands for the home-stretch negotiations, it has released a list of 11 points (pdf) it wants to discuss with the board.
These 11 points can be grouped into a smaller number of buckets: objections and disputes procedures, trademark protection, registry-registrar separation, and the treatment of geographical names.
I wrote about the trademark issue in part one of this post.
The GAC appears to have adopted many of the arguments of the IP lobby – it thinks the AGB does not currently do enough to ensure the costs to business of new TLDs will be minimized – so we might expect that to be a major topic of discussion at the GAC-Board retreat in February.
I’ll be interested to hear what it has to say about registry-registrar separation.
The GAC has been pushing for some looser cross-ownership restrictions, in order to foster competition, since 2007, and most recently in September.
It has previously been in favor of restrictions on “insider” companies with market power, but for a more relaxed environment for new entrants (such as “community” TLDs that may largely operate under agreements with their local governments).
This position looks quite compatible with ICANN’s new vertical integration policy, to me, so I’m not sure where the GAC’s concerns currently lie.
The issue of disputes and objections may be the trickiest one.
The GAC basically wants a way for its members to block “controversial” TLD applications on public policy grounds, without having to pay fees.
The “Rec6” policy, previously known as “morality and public order objections” is one of the issues the ICANN board has specifically acknowledged is Not Closed.
This is from its Cartagena resolution:

Discussions will continue on (1) the roles of the Board, GAC, and ALAC in the objection process, (2) the incitement to discrimination criterion, and (3) fees for GAC and ALAC-instigated objections. ICANN will take into account public comment including the advice of the GAC, and looks forward to receiving further input from the working group in an attempt to close this issue.

GAC members on the Rec6 working group repeatedly highlighted objection fees as a deal-breaker – governments don’t want to have to pay to object to TLD applications.
This appears to been cast as some kind of sovereignty-based matter of principle, although I suppose it could just as easily be an “in this economic climate” budgeting concern.
ICANN’s position is that the GAC as a whole can object for free, but that individual governments have to pay. Fees for some objection procedures will run into tens of thousands of dollars.
The GAC also has beef with the AGB’s treatment of geographic strings.
This is an area where ICANN says the AGB already “substantially reflects the views of the ICANN community” but intends to take GAC comments into account.
ICANN has already made substantial concessions on the geographic names issue, but there may still be a few loopholes through which territory names could slip through the net and be approved without the endorsement of their local governments.
Finally, the GAC wants to include amendments to the Registrar Accreditation Agreement, previously recommended by law enforcement agencies, in the AGB discussion.
The appears to have come completely out of the blue, without any direct relevance to the new TLD program.
It’s a long list covering a lot of issues, and it could get longer when the GAC publishes its official “scorecard”. We’ll have to wait and see.

Is ICANN too scared of lawsuits?

Kevin Murphy, November 17, 2010, Domain Registries

Arguments about the new top-level domain Applicant Guidebook kicked off with a jolt this week, when ICANN was accused of abdicating its responsibilities and being too risk-averse.
In what I think was the first case of a top ICANN staff member publicly discussing the AGB, senior veep Kurt Pritz fielded questions about “morality and public order objections” on a packed and occasionally passionate conference call (mp3).
On the call, Robin Gross of IPJustice accused ICANN’s of shirking its duties by proposing to “fob off” decisions on whether to reject controversial TLDs onto third-party experts.
She said:

I’m concerned that there’s a new policy goal – a new primary policy goal – which is the risk mitigation strategy for ICANN. I don’t remember us ever deciding that that was going to be a policy goal. But it seems that now what is in the best interest for the Internet is irrelevant. The policy goal that rules is what is in the best interest for ICANN the corporation

A cross-constituency working group (CWG) had said that controversial TLDs should be rejected only after a final nod from the ICANN board, rather than leaving the decision entirely in the hands of outside dispute resolution providers.
There was a concern that third parties would be less accountable than the ICANN board, and possibly more open to abuse or capture.
But ICANN rejected that recommendation, and others, on “risk mitigation” grounds. Explanatory notes accompanying the new AGB (pdf) say:

Independent dispute resolution is a cornerstone of the risk mitigation strategy. Without outside dispute resolution, ICANN would have to re-evaluate risks and program costs overall.

Almost a third of every new TLD application fee – $60,000 of every $185,000 – will go into a pool set aside for ICANN’s “risk costs”.
These costs were based on an estimate that there will be 500 applications, and that ICANN will need $30 million to cover risks.
These are often thought to be primarily risks relating to litigation.
There’s a fear, I suspect, that ICANN could become embroiled in more interminable .xxx-style disputes if it allows the board to make subjective calls on TLD applications, rather than hiring independent experts to make decisions based on uniform criteria.
On Monday’s conference call, Gross said that ICANN’s treatment of the CWG’s recommendations was a “really big shock”. She added:

clearly here this is just a fobbing off of that responsibility, trying to again avoid litigation, avoid responsibility rather than take responsibility and take accountability

But ICANN says that the risk mitigation strategy benefits TLD applicants by removing uncertainty from the program, as well making ICANN more credible.
Pritz said on the call:

the risk to the program is in creating a process or procedure that isn’t transparent and predictable for applicants. By what standard can a TLD be kicked out? It’s got to be: here’s the standards, here’s the decision maker and here’s the process.
When I talk about risk, it’s risk to this process.
If this process attracts a lot of litigation, and ICANN published the process and then did not follow it, or that the process wasn’t clear so that the applicant had no way of predicting what was going to happen to its application, the risk is then litigation would halt the process and undermine the ICANN model.
So it doesn’t really have anything to do with the people that are the directors or the people that are the staff; it has to do with the credibility of ICANN as a model for Internet governance.

In other words, if TLD applicants pay their fees and go into the process knowing what the rules are, and knowing that there’s little chance of being jerked around by the ICANN board, there’s less chance of the program as whole being disrupted by lawsuits.
Seems fair enough, no?

Will the new TLD guidebook provide answers?

Kevin Murphy, November 8, 2010, Domain Registries

ICANN is due to publish an Applicant Guidebook for new top-level domain registries tomorrow, and there are still big question marks over its contents.
Judging from a preliminary report from the ICANN board’s most-recent official meeting, some key decisions may not have yet been taken.
Perhaps the biggest unresolved issue is whether to permit the “vertical integration” of registry and registrar functions.
Which way ICANN swings on this problem will determine which companies are eligible to apply for new TLDs, how their business models will be structured, and how realistic “.brand” TLDs will be.
The ICANN community failed to reach consensus on this issue, largely due to differing business interests and a few consumer protection concerns.
But it looks like the ICANN board did not even discuss the matter at its October 28 meeting. The preliminary report has this to say:

2. Vertical Integration
In the interests of time, the Chair adjourned this item of discussion to a later date.

That “later date” may have been last Thursday and Friday, when the board held its rescheduled “retreat”, which is not designated as an official meeting.
On “Rec6”, previously known as the “morality and public order” objections process, the board passed no resolution October 28, but seems to have endorsed further discussions with the community.
The preliminary report states:

The Board discussed staff presentation and, in conformance with staff recommendation, directed staff to provide a briefing paper to the working group and to coordinate a call with the working group to further discuss the issues.

If the Rec6 working group mailing list and the GNSO calendar are any guides, that meeting has not yet been called (at least not publically).
The report also addresses geographic domains and issues that need to be taken into account given what ICANN’s Affirmation of Commitments with the US government says about new TLDs.

The Board agreed that staff provide a paper on geographic names to the GAC, the Chair of the GAC would check on the scope of issues still requiring discussion, and then the Chairs of the GAC and the Board would discuss the process for resolution to move this issue forward prior to Cartagena.

The Board discussed a paper regarding the adherence to the conditions set out in the Affirmation of Commitments in launching New gTLDs, and the need for identifying objective metrics to measure ICANN’s performance. The Board asked staff to consider what known performance indicators for the New gTLD program may be, what the adequacy scale is for measuring, and try to set that out for future conversation.

With all this in mind, it seems to me that while we may have a timeline for the launch of the new TLD program, there’s still much more to do than merely cross t’s and dot i’s.
Can we expect more placeholder text in tomorrow’s Applicant Guidebook?

.XXX debate could test GAC powers

Kevin Murphy, November 1, 2010, Domain Policy

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.

Former ICANN chief speaks out against new TLD morality veto

Kevin Murphy, October 26, 2010, Domain Policy

Former ICANN president and CEO Paul Twomey has expressed his support for rules curbing the ability of international governments to object to new top-level domains.
Twomey’s suggestions could be seen as going even further to limit government powers in the new TLD process than previous recommendations from the community.
The advice came during the ICANN comment period on the so-called “Rec6” recommendations, which previously sought to create an objection process based on “morality and public order” or “MOPO” concerns.
There had been a worry from some elements of the ICANN community that backwards governments could use Rec6 to arbitrarily block controversial new TLDs on national interest grounds.
But a cross-constituency working group, which included a few members of ICANN’s Governmental Advisory Committee, instead developed recommendations that would create a much narrower objections process with a greater emphasis on free speech.
Twomey, who quit ICANN in June 2009, has now expressed broad support for the working group’s recommendations, and suggests a few tweaks to make the process less open to abuse.
He said ICANN “should be careful not to view one government alone as having veto power over any particular gTLD string which is designed to serve a global or at least international user group”.
Notably, Twomey has urged ICANN to steer clear of the phrase “national interest”, which appears in the current Rec6 recommendations, and instead use “national law”.
He reasons that giving weight to “national interests” could enable fairly junior civil servants to object to new TLDs without the full backing of their governments or legislation.

phrases such as “perceived national interest” reflect a degree of political consideration which can be more fleeting, be expressed by very junior officials without Ministerial or Parliamentary approval, and often is a matter of debate between different groups within the country and government. In some respects it is similar to the phrase “public policy”. I remember a GAC member many years ago stating that “public policy is anything I decide it is”.

Twomey then recommends that even when a government has an objection based on an actual national law, that law “should only derive from a national law which is in accordance with the principle of international law.”
A law which violated human rights treaties, for example, or which was hurriedly passed specifically in order to scupper a TLD bid, would therefore not be valid grounds for objection.
Twomey’s reasoning here is fascinating and a little bit shocking:

without such a linkage, a unique, one-off power to a government would be open to gaming by well-funded commercial interests with political influence.

I am aware of some commercial entities involved in the ICANN space in years past that quietly boasted of their ability to get laws passed in certain small jurisdictions which would suit their commercial interests in competing with other players. This is not behaviour the ICANN Board should inadvertently incent.

I’ll leave it for you to speculate about which companies Twomey is referring to here. I don’t think there are many firms in the domain name space that well-funded.
Prior to becoming ICANN’s president, Twomey chaired the GAC as the Australian representative. He’s currently president of Leagle and managing director of Argo Pacific, his own consulting firm.
His full commentary, which delves into more areas than I can get into here, can be found here. The Rec6 working group’s recommendations can be found here (pdf). My previous coverage of the Rec6/MOPO issue can be found here.

ICANN to publish final new TLD rulebook before December

Kevin Murphy, September 26, 2010, Domain Registries

The ICANN board of directors said it will publish the final Applicant Guidebook for new top-level domains before the public meeting in Cartagena this December.
(UPDATE: that statement is not 100% accurate. See this post for an update.)
The decision came at the end of its two-day retreat in Trondheim, Norway yesterday, which seems to have left a number of important issues as yet unresolved.
The matters of registry-registrar cross ownership and morality and public order objections are both still unfinished business, while the intellectual property lobby has at least one bone thrown its way.
On the morality or “MOPO” problem, now known as the “Rec6” problem, the board had this to say:

The Board will accept the Rec6 CWG recommendations that are not inconsistent with the existing process, as this can be achieved before the opening of the first gTLD application round, and will work to resolve any inconsistencies.

The Rec6 working group had recommended a re-framing of the issue that would eliminate the possibility of any one government blocking a new TLD application based on its own laws and interests.
So the board resolution sounds like progress, until you realize that every decision on new TLDs made at the retreat is going to be re-evaluated in light of a shamefully eleventh hour wish-list submitted by the Governmental Advisory Committee on Thursday.
Having failed to get what it wanted through cooperation with the Rec6 working group, the GAC essentially went over the heads of the GNSO, taking its demands directly to the board.
So much for bottom-up policy making.

Resolved (2010.09.25.02), staff is directed to determine if the directions indicated by the Board below are consistent with GAC comments, and recommend any appropriate further action in light of the GAC’s comments.

In other words, the board may only accept the parts of the Rec6 recommendations that the GAC agrees with, and the GAC, judging from its latest missive, wants the first round of applications limited to purely “non-controversial” strings, whatever those may be.
The board also made no firm decision of the issue of registry vertical integration and cross-ownership. This is the entirety of what it said on VI:

The Board will send a letter to the GNSO requesting that the GNSO send to the Board, by no later than 8 October 2010, a letter (a) indicating that no consensus on vertical integration issues has been reached to date, or (b) indicating its documented consensus position. If no response is received by 8 October 2010, then the Board will deem lack of consensus and make determinations around these issues as necessary. At the time a policy conclusion is reached by the GNSO, it can be included in the applicant guidebook for future application rounds.

That’s actually borderline amusing, given that the GNSO working group on VI has recently been waiting for hints from the board about what it intends to do, rather than actually getting on with the job of attempting to create a consensus policy.
The bone I mentioned for the trademark crowd amounts to knocking a week off the length of time it takes to resolve a complaint under the Uniform Rapid Suspension policy.
The Trondheim resolutions also make it clear that the ICANN board will only be required to vote on a new TLD application in limited circumstances, such as when an objection is filed.
For all other applications, a staff mechanism for rapidly signing contracts and adding TLDs to the root will be created.

ICANN urged to kill new TLD morality veto

Kevin Murphy, September 17, 2010, Domain Services

ICANN has been asked to eliminate references to “morality and public order” objections from its new top-level domain application process.
A cross-constituency working group has advised ICANN’s board of directors to scrap the term and to ensure that whatever replaces it does not enable individual governments to veto new TLDs based on their own local laws.
The so-called “MOPO” or “MAPO” part of the Draft Applicant Guidebook attracted criticism because ICANN’s Governmental Advisory Committee seemed to want to use it to grant themselves the right to block any TLD application they deemed too controversial.
The fear from the GAC was that if nations started blocking whole TLDs at their borders, it could ultimately lead to the fragmentation of the DNS root.
The fear elsewhere was that some edgy TLD applications, such as .gay or .sex, could be rejected due to the unilateral objections of backward regimes, harming freedom of speech.
But if ICANN incorporates the working group’s new recommendations into the next version of the DAG, that probably won’t be allowed to happen.
The group this week forwarded an interim report to the ICANN board for its consideration. While incomplete, it already carries a few recommendations that managed to find consensus.
Notably, the report recommends that, “National law not based on international principles should not be a valid ground for an objection”, which would seem to scupper any chances of Uganda or the Holy See blocking .gay, for example.
The working group has so far failed to reach consensus on how governmental objections should be registered and processed, but one option is:

The Applicant Guidebook should allow individual governments to file a notification (not an objection) that a proposed TLD string is contrary to their national law. The intention is that an “objection” indicates an intent to block, but a “notification” is not an attempt to block, but a notification to the applicant and the public that the proposed string is contrary to the government’s perceived national interest. However, a national law objection by itself should not provide sufficient basis for a decision to deny a TLD application.

The working group, which counted a few GAC members among its number, has managed to unanimously agree that the awkward term “morality and public order” should be dumped.
One possible contender to replace it is “Objections Based on General Principles of International Law”.
The group has also discussed the idea that a supermajority vote could be required if the board decides to reject a TLD application based on a MOPO objection.
The report is a work in progress. The working group expects to send an updated document to the ICANN board shortly before its retreat later this month.
Whether any of this will be acceptable to the GAC as a whole is up for debate.

Governments want morality veto on new TLDs

Kevin Murphy, August 6, 2010, Domain Registries

ICANN’s Governmental Advisory Committee wants to be able to kill off new top-level domain applications on cultural and religious grounds.
The GAC has finally broken its radio silence on the “morality and public order” or “MOPO” issue that was such a hot topic at the Brussels meeting in June.
A letter to ICANN (pdf), sent by Canadian GAC chair Heather Dryden, leaves little room for doubt where the GAC stands.

The GAC firmly believes that the absence of any controversial strings in the current universe of top-level domains (TLDs) to date contributes directly to the security and stability of the domain name and addressing system (DNS) and the universal resolvability of the system.
As a matter of principle… the GAC believes that the object of stability, security, and universal resolvability must be preserved in the course of expanding the DNS with the addition of new top-level domains.

This is actually quite powerful stuff.
The GAC is basically saying that no new TLDs should be introduced that would be unacceptable to the lowest common denominator world government.
Think Uganda, asked to make a call on .gay.
Think about any oppressed ethnic group without a territory that wants to apply for its own TLD.
The GAC wants ICANN to create a process for governments and others to object to TLD applications on religious, cultural, linguistic, national and geographical grounds.
It could even result in .xxx being objected to, even though it’s technically part of the 2005 round of new TLDs – the GAC wants the objection process to apply to “all pending and future TLDs”.

Round-up of the ICANN new TLDs comment period

Today is the deadline to file comments on version four of ICANN’s Draft Applicant Guidebook for prospective new top-level domain registries.
Of the few dozen comments filed, the majority involve special pleading in one way or another – everybody has something to lose or gain from the contents of the DAG.
That said, I’ve read all the comments filed so far (so you don’t have to) and lots of good points are raised. It’s clear that whatever the final Applicant Guidebook contains, not everybody will get what they want.
Here’s a non-comprehensive round-up, organized by topic.
Trademark Protection
Trademark holders were among the first to file comments on DAG v4. As I’ve previously reported, Lego was first off the mark with an attempt to convince ICANN that the concerns of the IP lobby have not yet been resolved.
Since then, a few more of the usual suspects from the IP constituency, such as Verizon and InterContinental Hotels, have filed comments.
The concerns are very similar: the Universal Rapid Suspension process for trademark infringements is too slow and expensive, the Trademark Clearinghouse does not remove cost or prevent typosquatting, not enough is done to prevent deadbeat registries.
Verizon, a long-time opponent of the new TLD program and a rigorous enforcer of its trademarks, used its letter to raise the issue of cybercrime and hit on pressure points relating to compliance.
It brings up the KnujOn report (pdf) released in Brussels, which accused ICANN registrars of being willfully blind to customer abuses, and the fact that ICANN compliance head David Giza recently quit.
Two IP-focused registrars also weighed in on trademark protection.
Com Laude’s Nick Wood filed a very good point-by-point breakdown of why the URS process has become too bloated to be considered “rapid” in the eyes of trademark holders.
Fred Felman of MarkMonitor covers the same ground on rights protection mechanisms, but also questions more fundamentally whether ICANN has shown that the new TLD round is even economically desirable.
Felman has doubts that new gTLDs will do anything to create competition in the domain name market, writing:

the vast majority of gTLDs currently being proposed in this round are gTLDs that hide traditional domain registration models behind a veil of purported innovation and creativity

Well, I guess somebody had to say it.
Fees
There are concerns from the developing world that $185,000, along with all the associated costs of applying for a TLD, is too steep a price to pay.
The “African ICANN Community” filed a comment a month ago asking ICANN to consider reducing or waiving certain fees in order to make the program more accessible for African applicants.
Several potential TLD registries also think it’s unfair that applicants have to pay $185,000 for each TLD they want to run, even if it’s basically the same word in multiple scripts.
Constantine Roussos, who intends to apply for .music, reiterated the points he brought up during the ICANN board public forum in Brussels last month.
Roussos believes that applicants should not have to pay the full $185,000 for each non-ASCII internationalized domain name variant of their primary TLD.
He wrote that he intends to apply for about six IDN versions of .music, along with some non-English Latin-script variants such as .musique.
Antony Van Couvering of registry consultant Minds + Machines and .bayern bidder Bayern Connect both echo this point, noting that many geographical names have multiple IDN variants – Cologne//Koeln/Köln, for example.
Roussos also notes, wisely I think, that it appears to be a waste of money paying consultants to evaluate back-end registry providers for applicants who choose to go with an recognized incumbent such as VeriSign, NeuStar or Afilias.
Another request for lower fees comes from the Japan Internet Domain Name Council, which thinks geographical TLD applications from small cities should receive a discount, as well as a waiver of any fees usually required to object to a third-party application.
Contended Strings and Front-Running
Of the known proposed TLDs, there are several strings that will very likely be contended by multiple bidders. This has led to maneuvering by some applicants designed to increase their chances of winning.
Roussos suggested that applicants such as his own .music bid, which have made their plans public for years, should be awarded bonus points during evaluation.
This would help prevent last-minute con artists stepping in with “copy-paste” bids for widely publicized TLDs, in the hope of being paid off by the original applicant, he indicated.
Roussos thinks the amount of work his .music has done in raising community awareness around new TLDs has earned the company extra credit.
It’s a thought echoed by Markus Bahmann, dotBayern’s chairman, and his counterpart at dotHamburg.
The opposing view is put forward by rival .bayern bidder Bayern Connect’s Caspar von Veltheim. He reckons such a system would put “insiders” at an unfair advantage.
M+M’s Van Couvering also said he opposes any applicant getting special treatment and added that M+M wants an explicit ban on trademark front-running included in the DAG.
Front-running is the practice of registering a TLD as a trademark in order to gain some special advantage in the new TLD evaluation process or in court afterward.
(M+M’s owner, Top Level Domain Holdings, has reportedly been front-running itself – attempting to defensively register trademarks in the likes of .kids, .books and .poker, while simultaneously trying to fight off similar attempts from potential rivals.)
Roussos of .music responded directly to M+M this afternoon, presenting the opposite view and promising to use its trademarks to defend itself (I’m assuming he means in court) if another .music applicant prevails.

Rest assured that if we, as .MUSIC are faced with the possibility of being gamed and abused in a manner that we find illegal, we will use our trademarks and other means necessary to do what we have to do to protect ourselves and our respective community.

He said .music is trademarked in 20 countries.
Morality and Public Order
This was a hot topic in Brussels, after the ICANN Governmental Advisory Committee agreed that it did not like the “MOPO” objection provisions of DAG v4, but could not think of a better replacement.
MOPO would give a way for governments to scupper bids if they do not like the morality implications. Anybody applying for .gay, for example, would have to deal with this kind of nonsense.
Jacob Malthouse of BigRoom, one of the would-be .eco bidders, reckons ICANN should treat the GAC the same as it treated the GNSO on the issue of vertical integration – remove MOPO from the DAG entirely in order to force the GAC to come up with something better.
The GAC had previously said it would address the MOPO issue in its comments on DAGv4, but its filing has not yet appeared on the ICANN site.
There’s a GNSO working group over here, but M+M’s Van Couvering notes that no GAC members have got involved post-Brussels.
Terrorism
Two commentators objected to the idea that an applicant could be rejected for involvement in “terrorism”, a term that DAGv4 does not define.
I reported on this a few days ago, but since then Khaled Fattal of the Multilingual Internet Group has filed a surprising rant that seems to indicate he has way more beef than really necessary.
Here’s a few quotes mined from the full comment:

it will alienate many in the international community who will choose not to take part in future ICANN processes including its New gTLDs, distrusting ICANN’s motives, or actively choosing to boycotting it, and causing many to seriously start re-considering alternatives.

as a Syrian born Arab American would I pass the IvCANN terrorism verification check as they are? After all Syria, my country of birth, is on the U.S. Government list of states sponsor of terrorism? And I admit, I do know an “Osama”, does that disqualify me? I Forgot to add, “Osama Fattal” a cousin. So would I pass or fail this check?

The arbitrary inclusion of terrorism as a measuring stick without any internationally recognized laws or standards is wrong and offensive to many around the world. If acted upon, it will be seen by millions of Muslims and Arabs as racist, prejudicial and profiling and would clearly indicate that ICANN has gone far beyond its mandate.

Vertical Integration and .brand TLDs
The issue of whether registries and registrars should be allowed to own each other is a thorny one, but there’s barely any mention at all of it in the DAGv4 comments filed so far.
The DAGv4 language on VI, which effectively bans it, is a place-holder for whatever consensus policy the GNSO comes up with (in the unlikely event that its working group ever gets its act together).
Most efforts on VI are therefore currently focused in the GNSO. Nevertheless, some commentators do mention VI in their filings.
Roussos of .music wants .music to be able to vertically integrate.
Abdulaziz Al-Zoman of SaudiNIC said VI limits should be removed to help applicants who need to turn to third-party infrastructure providers.
From the IP lobby, Celia Ullman of cigarette maker Philip Morris notes that there’s nothing in DAGv4 about single-registrant .brand TLDs. She writes:

would this mean that trademark owners owning a gTLD would need to open the registration procedure to second-level domain names applied for to third unrelated parties? In this case, what would be the incentive of actually registering and operating such a gTLD?

Clearly, the idea that a .brand would have to be open to all ICANN registrars on a non-discriminatory basis is enough to make any trademark attorney choke on their caviare.
JPNIC, the .jp ccTLD operator, also points out that DAGv4 says next to nothing about .brand TLDs and strongly suggests that the final Applicant Guidebook spells out just what a registry is allowed to do with its namespace (lawsuits are mentioned)
Disclaimer
I’ve paraphrased almost everybody in this article, and I’ve done it rather quickly. Despite my best efforts, some important nuance may have been lost in the act.
If you want to know what the commentators I’ve cited think, in their own words, I’ve linked to their comments individually throughout.
I may update this post as further comments are filed.