Latest news of the domain name industry

Recent Posts

Round-up of the ICANN new TLDs comment period

Kevin Murphy, July 21, 2010, 16:16:04 (UTC), Domain Registries

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.

Tagged: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Comments (9)

  1. Useful summary. You kind of gave short shrift to the working group on vertical integration – understandable, as its a complex situation. those wanting a summary of where that WG is can look here.

    • Kevin Murphy says:

      Thanks Milton.

      On VI, I’ve kinda been waiting for the “end product” to come out before going into any depth. Trust me when I say I’ve been following the WG’s work fairly closely.

  2. Kevin,

    Your big effort in summarizing all comments is noted so is your calling my letter to ICANN a “rant”, which made me laugh. My question is: Would you feel the same way if you were a member of the 1.5 billion Muslims around the world who for decades have been racially profiled against and now will be racially profiled against by ICANN without standard or definition? The international press seems to feel my letter has great validity and covered it in multiple languages, while ICANN remains silent. Maybe you are right and they all are wrong. Warmest.

    • Kevin Murphy says:

      Thanks for the feedback Khaled.

      Clearly, there’s no way for me to know how I’d feel if I were a Muslim.

      I do, however, believe that you may be making a mountain out of a molehill here.

      To my mind, and with respect, to automatically equate the inclusion of the word “terrorism” in the DAG with “racism” takes more than a small stretch of the imagination.

      I do not believe there’s any need to play the race card in order to have your concerns — which for the sake of clarity in the DAG I think have merit — looked into.

      And ICANN has not of course remained silent. Kurt Pritz, for one, addressed your concerns publically during the Brussels meeting on more than one occasion, promising to define the term or remove it from the DAG.

  3. Kevin,

    Kurt Pritz said it was added based on experts ICANN consulted, so who are these experts? and what experts recommend any verification of anything without clear definition or standard? ICANN should be asking for their money back and exposing these pretending experts LOL.

    Kurt could have earned his wages if he had added to the document before releasing it that clear definitions will be added based on extensive feedback at later stages, well he did not. At a minimum, this can be called “sleeping at the wheel” and it is not good conduct of an allegedly transparent bottom up organization ICANN always reminds us it is.

    In any case, thank you Kevin for your honesty in replying that there’s no way for you to know how you would feel if you were a Muslim, but I am sure you have heard of innocent civilians who end up getting bombed to smithereens in the name of freedom in some far away land based on allegations of or bad Intel of terrorism. I am doing my part in removing another excuse to more of the same.

    And by the way you have helped as well by elevating the awarness level on this subject. My compliments. (end my other rant 😉

    warmest,

    Khaled

    • Kevin Murphy says:

      “I am sure you have heard of innocent civilians who end up getting bombed to smithereens”

      Yes. I have.

      And if you think you can make a half-convincing case about why that has any relevance to the domain name industry, I’d love to hear about it.

      • One day maybe over a coffee. but we seem to be talking about 2 different things, you seem to see this pertaining to the domain name industry and ICANN’s role, I don’t, to me this is about the global internet, Internet Governance, etc.

        best of luck

  4. […] Fattal of the Multilingual Internet Group told ICANN it would “be seen by millions of Muslims and Arabs as racist, prejudicial and […]

Add Your Comment