.taipei not blocked after all

Taipei City Government’s application for the .taipei new gTLD is still live, despite indications to the contrary from ICANN last week.
On Friday, we reported that there was some confusion about the status of the bid, which was flagged by ICANN as “Eligible for Extended Evaluation” in one place and “Ineligible for Further Review” in another.
We wondered aloud whether Taiwan’s controversial national identity was responsible for the application failing due to lack of governmental support.
But an ICANN spokesperson called last night to confirm that the “Eligible” status is the correct one. The ICANN web site has been corrected accordingly.
What this means is that .taipei is not rejected yet, but must provide more evidence of government support if it wants to pass Extended Evaluation and eventually get delegated.
The question remains, however: which government are we talking about here? If it’s the People’s Republic of China, which claims Taiwan as a province, Taipei may still face problems.

Comment Tagged: .taipei, ICANN, new gTLDs

CNNIC hit by “largest ever” denial of service attack

Chinese ccTLD operator CNNIC suffered up to half a day of degraded performance and intermittent accessibility yesterday, after being hit by what it called its “largest ever” denial of service attack.
CNNIC is one of ICANN’s three Emergency Back-End Registry Operators, contracted to take over the running of any new gTLD registries that fail. It’s also the named back-end for seven new gTLD applications.
According to an announcement on its web site, as well as local reports and tips to DI, the first wave of DDoS hit it at about midnight yesterday. A second wave followed up at 4am local time and lasted up to six hours.
According to a tipster, all five of .cn’s name servers were inaccessible in China during the attack.
Local reports (translated) say that many Chinese web sites were also inaccessible to many users, but the full scale of the problem doesn’t seem to be clear yet.
China’s .cn is the fourth-largest ccTLD, with close to 10 million domains under management.

Comment Tagged: cnnic, ddos, ebero, ICANN, new gTLDs

dotShabaka Diary — Day 6, TMCH Integration Testing

Today, the sixth installment of dotShabaka Registry’s journal, charting its progress towards becoming one of the first new gTLDs to go live, written by general manager Yasmin Omer.

Monday 26 August 2013
We attended the second IBM webinar on the TMCH which ran smoothly. The guys at IBM were pretty responsive and helpful.
Having received our registration token from ICANN, we logged on to the TMDB System to create credentials for the OT&E platform, provide contact details and accept the TMCH Terms and Conditions. TMCH integration testing is now on hold since we were not able to download the DNL file or upload the LORDN file. IBM confirmed that this functionality will not be available until the Trademark Claims functionality update scheduled for the 9th of September.
The testing environment was communicated as the TMCH accreditation environment that would include all the functionality required for Sunrise processing. It’s currently a limited test environment but we’re looking forward to conducting further tests as IBM continue to add functionality.
We recommend those planning on conducting TMCH Integration Testing in the near future wait until the Claims functionality update scheduled for the 9th of September before proceeding.

Read previous and future diary entries here.

Comment Tagged: dotshabaka diary

Failures mount up as ICANN releases penultimate week of IE results

Eight new gTLD applications flunked Initial Evaluation this week, according to ICANN’s just-released results.
One of them, the Taipei City Government’s bid for .taipei, has been flagged as “Ineligible for Further Review” — the only application to receive such a status to date — suggesting it is fully dead.
But the full IE report delivered by ICANN says .taipei is actually “Eligible for Extended Evaluation”. It’s not clear right now which of these statuses is the correct one.
Its IE report says “the required documentation of support or non-objection was either not provided or did not meet the criteria” for Taipei’s bid to pass the Geographic Names Review.
While the city government seems to be the applicant, city bids also require national government support, which could be problematic given that the People’s Republic of China regards Taiwan as a province and the United Nations does not officially recognize it as a nation.
Also failing to receive a passing score this week was one of three bidders for the hotly contested gTLD .eco.
Planet Dot Eco failed on both its financial and technical questions, one of the first two applicants to suffer this double whammy. The other was Metaregistrar, which has just found out its app for .frl has failed on both counts.
The clothing retailer Express, noted for its failed Legal Rights Objection against Donuts, also failed its technical evaluation.
Express had a Verisign back-end, while Planet Dot Eco is using ARI Registry Services. Metaregistrar did not specify a third-party back-end provider in its application.
.olayan became the third application from the Saudi conglomerate Olayan Investments to fail because it did not provide its financial statements as required by the Applicant Guidebook.
.place, an application by 1589757 Alberta Ltd (‘DotPlace’) also failed to provide financial statements, as did the dot-brands .shaw, .alcon and .rexroth.
These applications received passing scores this week:

.mail .tech .kpn .play .weatherchannel .crown .aeg .statoil .app .cloud .honeywell .cruises .vig .netaporter .juegos .aramco .lamborghini .soccer .ping .surf .lol .gallo .parts .flowers .gree .webs .netflix .science .school .inc .rio .bbt .mutual .auspost .best .men .symantec .med .doctor .deals .insure .citadel .care .barcelona .racing .feedback .amfam .design .save .nhk .productions .forum .finish .spot .hitachi .web .dish .vistaprint .art .maison .properties .nissay .book .tiffany .haus .skin .hockey .phone .allfinanz .finance .通用电气公司 .手表 .電訊盈科 .珠宝 .ارامكو .hisamitsu .intuit .orientexpress .gecompany .team .church .panasonic .onyourside .ski

With only 141 applications left in evaluation, there’s only one week officially left on the IE timetable, though I expect ICANN will spend some time mopping up the stragglers afterwards.
There are 23 applications eligible for extended evaluation.

Comment Tagged: ICANN, initial evaluation, new gTLDs

Bank takes blame for gTLD name collision

The Commonwealth Bank of Australia, which has applied for the new gTLD .cba, has told ICANN that its own systems are to blame for most of the error traffic the string sees at the DNS root.
The company wants ICANN to downgrade its gTLD application to “low risk” from its current delay-laden “uncalculated” status, saying that it can remediate the problem itself.
Since the publication of Interisle Consulting’s name collisions report, CBA said it has discovered that its own systems “make extensive use of ‘.cba’ as a strictly internal domain.”
Leakage is the reason Interisle’s analysis of root error traffic saw so many occurrences of .cba, the bank claims:

As the cause of the name collision is primarily from CBA internal systems and associated certificate use, it is within the CBA realm of control to detect and remediate said systems and internal certificate use.

One has to wonder how CBA can be so confident based merely on an “internal investigation”, apparently without access to the same extensive and highly restricted data set Interisle used.
There are many uses of the string CBA and there can be no guarantees that CBA is the only organization spewing internal DNS queries out onto the internet.
CBA’s comment is however notable for being an example of a bank that is so unconcerned about the potential risks of name collision that it’s happy to let ICANN delegate its dot-brand without additional review.
This will surely help those who are skeptical about Interisle’s report and ICANN’s response to it.

2 Comments Tagged: .cba, commonwealth back of australia, ICANN, name collisions, new gTLDs, security

.vip and .now clear objections

The latest batch of Legal Rights Objection results has seen two proposed new gTLDs — .vip and .now — emerge unscathed from the objections phase of the new gTLD program.
There are six applications for .vip and one of the applicants, I-Registry, had filed LROs against its competitors.
Starbucks (HK), a cable company rather than a coffee chain, had also filed LROs against each of its five rivals for .now.
With yesterday’s decisions, all 10 objections have now been rejected.
In the case of .vip, every applicant wants to run it as a generic term, but I-Registry had obtained a European trademark on its proposed brand.
But Starbucks’ .now was to be a dot-brand reflecting a pre-existing mark unrelated to domain names. WIPO panelists found that trademark did not trump the proposed generic use by other applicants, however.
Both strings will now head to contention resolution, where an auction seems the most likely way to decide the winners.

1 Comment Tagged: .now, .vip, i-registry, ICANN, legal rights objection, new gTLDs, starbucks, wipo

Panel says .sport and .sports are confusingly similar

Olympics-backed new gTLD applicant SportAccord has won a String Confusion Objection against Donuts, with an arbitration panel finding that .sport and .sports are too similar to coexist.
It’s the second SCO case involving a plural to go against Donuts, after the shock .pet/.pets decision last week.
While the judgment is sure to fuel the debate about singular and plural gTLD coexistence, the strings in question in this case do have some unique characteristics.
As panelist M Scott Donahey noted, .sport is both singular and a collective noun, making it essentially a plural and synonymous with .sports.
The sentences “I like sports” and “I like sport” both make sense and mean the same thing. The same could not be said for, for example, “I like car” or “I like pet”.
Donahey was also persuaded by the argument that because “sport” is also a French word meaning the same thing, the fact that “sports” and “sport” are pronounced the same in French means the two strings confusingly similar aurally. He wrote:

The convergence of all these similarities, the fact that the words look very similar in English and sound the same in French, and that the words can be used interchangeably as nouns in English to indicate the panorama of sporting activities, and that the words are interchangeable when used as adjectives in English, all lead the Expert to conclude that it is probable that confusion will arise in the mind of the average, reasonable internet user.

The panelist had access to the rulings in the .pets v .pet case (cited by SportAccord) and the .car v cars case (which went the other way and was cited by Donuts).
Donahey’s ruling is notable also because of what he explicitly declined to consider, namely: the possible harms that could be created by string confusion. He wrote:

Objector’s many references to possible fraud, deceit, cybersquatting or other types of abuse through the use of the gTLD proposed by Applicant are in the nature of a legal rights objection, and mere speculation, and are unworthy of any consideration by an Expert in a string confusion analysis.

In other words, he focused just on the visual, aural and semantic similarity of the two strings. It’s going to be hard for anyone to argue that he overstepped the bounds of an SCO, which has happened following other decisions.
All in all it seems like a pretty sensible decision (pdf). It’s hard to fault Donahey’s logic.
(As an aside, I’ve started to notice that the SCO decisions with the soundest reasoning seem to be coming from panelists, such as Donahey, with extensive experience adjudicating UDRP complaints).
If the ruling stands — that is, if ICANN does not reopen the plurals/singulars policy debate — Donuts’ application for .sports will be forced into a contention set with the two applications for .sport.

1 Comment Tagged: .sport, .sports, donuts, icdr, plurals, sco, sportaccord, string confusion objection

New gTLDs: 23 community objections withdrawn

Almost a quarter of Community Objections against new gTLDs have been terminated without a decision, according to International Chamber of Commerce documentation.
The withdrawals leave the way open for the applied-for gTLDs .insure, .realty, .realestate, .cruises, .careers and .bio to proceed unencumbered by any objections at all.
In total 23 Community Objections, of the original 104 reported by ICANN, have been dropped. Two of the original 23 Limited Public Interest Objections have also been terminated, according to the ICC.
The terminated Community Objections seem to fall into a few categories.
Objections against applications for .autoinsurance, .carinsurance, .health, .mail and .patagonia appear to have been stopped because the applications themselves were withdrawn.
The Independent Objector, Alain Pellet, has withdrawn one Limited Public Interest — .health — and three Community objections — .patagonia, .indians, .hospital.
These seem to have been yanked due to either application withdrawals, matching objections filed by third parties, or by Governmental Advisory Committee advice.
Applications facing one fewer objection — but not zero objections — include those for .insurance, .broker, .hoteis, .hoteles, .health, and .kid.
GAC advice remains a concern for many of the affected applicants, even those that no longer face the uncertainty and expense of the objection process.
Donuts seems to have fared best from the terminations. Its .careers and .cruise bids seem to be the only ones to have emerged uncontested and with no outstanding objections or GAC advice.
The terminations were revealed in an updated list of objections published by the ICC on Monday.
The updated data is now indexed and searchable on the all-new, super-duper DI PRO Application Tracker.

7 Comments Tagged: community objection, ICANN, icc, independent objector, international chamber of commerce, limited public interest objection

GM down to one gTLD bid after dropping .chevy

General Motors looks set to leave the new gTLD program completely, after dumping its application for .chevy.
It’s the fourth of GM’s five dot-brand gTLD bids to be withdrawn after .chevrolet, .cadillac and .gmc. Only .buick remains in the Initial Evaluation process.
Of the 116 new gTLD applications to be withdrawn to date, 55 have been uncontested and for single-registrant zones. Almost all of the 55 applied-for strings are famous brands.
It would be wrong to assume that each of these was a “defensive” application — some represent discontinued brands — but it’s still a worryingly high number, representing over $10 million in ICANN fees.
That said, it’s still less than 3% of the total applications submitted in the current round.

Comment Tagged: .chevy, dot-brands, general motors, gm, withdrawals

Registrar rapped for failing to transfer UDRP domain

The domain name registrar Gal Comm has been warned by ICANN that it risks losing its accreditation for failing to transfer a cybersquatted name to Home Depot.
The compliance notice (pdf) concerns the domain name homedpeot.com, which was lost in a UDRP filed in early March and decided on April 21.
According to ICANN, Gal Comm, which has about 30,000 gTLD domains under management, failed to transfer the domain within 10 days of finding out about the decision, as required under the policy.
Whois records compiled by DomainTools show that the domain was instead deleted at in early April, and subsequently re-registered with a different registrar, where it’s currently under dubious-looking privacy.
According to the ICANN compliance notice, Gal Comm says that it deleted the domain because it received a Whois inaccuracy complaint about it.
Assuming that’s correct (and the Whois back in March was blatantly false) we have an interesting tension between policies that seems to have caused a slip-up at the registrar.
But registrars are supposed to lock domains they manage after they become aware of UDRP actions, so allowing the domain to delete seems to be a breach of the policy.
ICANN has given Gal Comm until September 10 to produce its records relating to the domain — and pay past-due accreditation fees — or face possible de-accreditation.
It’s very rare for ICANN to send compliance notices to registrars related to UDRP implementation.

1 Comment Tagged: compliance, gal comm, homedpeot.com, ICANN