Why is ICANN’s Ombudsman trying to take down a drink-drive mugshot?

Apparently there wasn’t already enough confusion about ICANN’s role in internet governance.
ICANN’s independent Ombudsman, Chris LaHatte, seems to be getting involved in content-related arguments between netizens and web site operators, according to a new case report posted on his blog.
LaHatte recently received a complaint from an internet user about the web site Busted Mugshots, a search engine for US criminal records.
The complainant was a professional who in his younger days had been pulled over for drink-driving and photographed by police, but never charged or convicted of any offense.
Busted Mugshots had apparently tried to charge him a fee and demanded to see non-existent court acquittal documents in order to remove his photograph from the site.
I’m assuming the individual in question complained to the Ombudsman because he has no idea what powers ICANN has or what the ICANN Ombudsman’s role is.
ICANN, for avoidance of doubt, has no powers over the content of web sites, and the Ombudsman’s job is to investigate complaints about ICANN’s actions or decisions.
Yet LaHatte, perplexingly, got involved anyway.
According to his case notes he contacted Busted Mugshots to point out that it was very unfair to keep the complainant’s photo up, but met with the same response as the complainant.
I’ve no doubt that LaHatte’s heart was in the right place here, and he says he pointed out at all times that he has no jurisdiction over web content, but I can’t help but worry that this doesn’t help ICANN’s image.
You only need to lurk on a Twitter search for “icann” for a day or two — or read some non-industry media coverage for that matter — to know that lots of people out there don’t know what ICANN does.
Many regular internet users mistakenly believe the organization is the internet’s government or police force, and ICANN has done a pretty poor job over the years of correcting misconceptions.
While I’m sure no one would challenge LaHatte’s right to complain about the contents of web sites as a private citizen, I don’t think the Ombudsman should be seen to be involving himself in this kind of dispute.

Straw man proposed to settle trademark deadlock at secretive ICANN meeting

Trademark interests seem to have scored significant concessions in their ongoing battle for stronger rights protection mechanisms in new gTLDs, following a second closed-doors ICANN meeting.
Following a two-day discussion of the Trademark Clearinghouse in Los Angeles late last week, ICANN CEO Fadi Chehade has published a “straw man” proposal for further discussions.
The straw man — if it is ultimately adopted — would grant the Intellectual Property Constituency and Business Constituency some of the things they recently asked for.
Crucially, they’d get the right to add keywords to the trademarks they list in the Trademark Clearinghouse, making them eligible for the Trademark Claims service.
There would be a test — a UDRP or court win concerning the string in question — for inclusion, and a limit of 50 brand+keywords or misspellings per trademark in the Clearinghouse.
The idea here is to help brand owners quickly respond to the registration of — but not preemptively block — domains such as “brand-industry.tld” or “brand-password-reset.tld”.
The Trademark Claims service would be extended from 60 to 90 days, under the straw man model.
Chehade’s blog post also outlines a “Claims 2” process that would run for six to 12 months after the launch of each new gTLD and would require trademark owners to pay an additional fee.
This Claims 2 service would not necessarily give registrants the same information about trademarks related to the domains they want to registry. Why not is anyone’s guess.
Here’s how Chehade described it:

Rights holders will have the option to pay an additional fee for inclusion of a Clearinghouse record in a “Claims 2″ service where, for an additional 6-12 months, anyone attempting to register a domain name matching the record would be shown a Claims notice indicating that the name matches a record in the Clearinghouse (but not necessarily displaying the actual Claims data). This notice will also provide a description of the rights and responsibilities of the registrant and will incorporate a form of educational add-on to help propagate information on the role of trademarks and develop more informed consumers in the registration process.

I’ve long been of the opinion that Trademark Claims service will not prevent most cybersquatting (determined bad actors will click through the notices as easily as you or I click through a software license agreement) and “Claims 2” appears to be a diluted version of the same lip service.
Claims 2 and the extension of the Clearinghouse to brand+keyword strings appears to be a step in the right direction for trademark owners, but I can’t see the changes substantially reducing their costs.
There’s also already opposition to the ideas from the Non-Commercial Stakeholders Group, according to this analysis of the straw man from NCSG chair Robin Gross.
The LA meeting rejected the notion of a preemptive cross-TLD trademark block list along the lines of the ICM Registry’s Sunrise B for .xxx, which is among the IPC/BC proposals.
The only change to Sunrise proposed in the straw man model is a mandatory 30-day notice period before the mandatory 30-day Sunrise kicks off, to give brand owners time to prepare.
In summary, the straw man proposal appears to create some marginal benefit for trademark owners at the expense of some additional cost and complexity for registries and registrars.
It would also create an entirely new rights protection mechanism — Claims 2 — out of whole cloth.
While no firm decisions appear to have been made in LA, it’s impossible for us to know for sure what went down because the meeting was held behind closed doors.
ICANN even enforced a Twitter ban, according to some attendees.
The meeting was the second private, invitation-only TMCH discussion in recent weeks.
While we understand there were remote participation opportunities for invited guests unable to attend in person, there was no opportunity to passively listen in to the call.
DI was told by ICANN there was no way for us to follow the talks remotely.
According to a number of attendees on Twitter, participants were also asked by ICANN not to tweet about the substance of the discussions, after complaints from trademark interests present.
The same attendees said that ICANN plans to publish a transcript of the meeting, but this has not yet appeared.
Considering that the issues under discussion will help to shape the structure of the domain name industry for many years to come, the lack of transparency on display is utterly baffling.

Pritz’s conflict of interest was with ARI

Former ICANN chief strategy officer Kurt Pritz had a conflict of interest related to back-end registry provider ARI Registry Services, DI can reveal.
Pritz resigned last week after disclosing the potential conflict to CEO Fadi Chehade, leading to a great deal of industry speculation about the specific nature of the problem.
Chehade revealed to attendees at an unrelated community meeting at ICANN headquarters in Los Angeles last Thursday that the conflict was of a “personal” nature.
Since then, I’ve managed to uncover the basic facts of the story – more than enough to confirm that it’s a personal issue and to establish that there do not appear to be any financial conflicts.
So I’ve decided not to report the full details, other than to say the conflict relates to ARI Registry Services, a major provider of back-end registry services for new gTLD applicants.
Pritz, as senior vice president for stakeholder relations and then chief strategy officer, was for a long time the key ICANN executive overseeing the new gTLD program.
I understand that the conflict was voluntarily disclosed by Pritz.
He also appears to have been held to at least as high a standard of ethics as ICANN’s own board of directors.
While ICANN clearly determined that there was a risk of a perception of a conflict of interest, I’ve discovered no reason to believe there was any actual wrongdoing by ICANN, ARI or Pritz.
The recent public record does not appear to reveal any instances of Pritz giving any special treatment to ARI. If anything, I believe the evidence would most likely lead to the opposite conclusion.
For example, during recent Trademark Clearinghouse implementation talks, Pritz was staunchly opposed to key aspects of a community solution co-developed by ARI.
As reported last month, these talks were notable for Pritz’s attempts to block some important parts of the community proposal, despite aggressive lobbying by ARI executives.
In short, I don’t think there’s a conspiracy here.
It’s my belief that Pritz’s resignation is the result of an unfortunate set of circumstances occurring at an organization that is – understandably – hyper-sensitive to negative perceptions about its integrity.

New gTLD guru Kurt Pritz quits ICANN over conflict of interest

ICANN’s recently promoted chief strategy officer Kurt Pritz has resigned, citing a conflict of interest.
The shocking news came in a message from CEO Fadi Chehade, posted this afternoon to the ICANN web site.
Here is the message in its entirety:

To the ICANN Community,
Regretfully, I have accepted the resignation of Kurt Pritz, who has served most recently as ICANN’s Chief Strategy Officer.
Kurt has submitted his resignation because of a recently identified conflict of interest, which he immediately communicated to ICANN. After analyzing this conflict of interest, we decided that a change in Kurt’s role within ICANN would be appropriate. Kurt decided to resign his position and role as an officer of ICANN, to best serve the interests of the organization. Kurt will be engaged as a subject matter expert where needed, but will have no access to new gTLD applicant information nor will he play a role in the new gTLD program.
I have already put in place a plan for the reassignment of all of Kurt’s management responsibilities.
I would like to thank Kurt for his many years of service and commitment to ICANN and our community.
Respectfully,
Fadi

No further details were provided.
Pritz was until recently senior vice president for stakeholder relations. He was elevated to the newly created C-level position when Chehade joined ICANN in October.
He’s been ICANN’s point man for the new gTLD program for years, and his departure will be a huge loss to the organization.
His resignation follows that of new gTLD program manager Michael Salazar, who took the fall for the aborted Digital Archery fiasco this June, and comes shortly after Chehade’s incoming management shake-up.
UPDATE: Pritz, in an email to DI, declined to comment and referred questions to ICANN.
UPDATE 2: ICANN has so far declined to elaborate on the reasons for Pritz’s resignation, saying it is a “personnel matter”.
However, according to multiple sources attending an unrelated meeting at ICANN’s headquarters in Los Angeles today (discussing the Trademark Clearinghouse), a couple of hours ago Chehade disclosed that Pritz’s conflict was of a “personal”, rather than professional, nature.

Six more new gTLD applications yanked

A further six new gTLD applications have been withdrawn from evaluation, bringing the total to 13, according to ICANN.
The identities of the newly yanked bids is not known as they’ve not yet been fully processed. Of the 13, only .and, .are, .est, .chatr, .ksb and .cialis have been named so far.
The news emerged in a presentation ICANN is set to use in its monthly webinar for applicants shortly.
The presentation also confirms that there have been no official objections filed against any applications yet.
The String Similarity Review — which will create the initial contention sets among similar strings — has been completed, ICANN also revealed, but results will not be published until a secondary review has ended.
All applications have passed the DNS Stability Review, which checks whether the string itself could cause any DNS problems, ICANN said.
This is pretty big news for the .home applicants, to name just one string. It had been suggested that .home would cause problems because it also receives a substantial amount of traffic in the root servers.
At least one major ISP I’m aware of, Britain’s BT, uses .home as a local TLD in its residential hubs.
ICANN has also revealed that some applicants have not yet cleared background screening, saying:

Initial background screening review has been completed. The background screening service provider has identified some applications where additional information is required in order to continue with the review. Applicants for these applications will be contacted soon through the CSC [Customer Service Center] to provide the additional information.

The date of the Draw for application prioritization has been confirmed as December 17.
The webinar kicks off here at 2000 UTC today.

ICANN expecting to approve most new gTLDs?

Good news for new gTLD applicants?
ICANN appears to be assuming that the vast majority of applications will pass their evaluations and make it at least as far as pre-delegation testing, judging from recent comments.
Of the 1,400-odd unique strings being applied for, ICANN reckons that “close to the maximum” will need to be tested before being added to the DNS root.
The hint came in a Q&A with respondents to ICANN’s pre-delegation testing provider RFP published yesterday.
With added emphasis, here’s what ICANN just said:

Question 7: Can ICANN provide a definitive statement of the anticipated minimum number of pre-delegation tests?
The total number of applied-for strings that will be approved is unknown at this point. Therefore, we cannot assert the minimum number of registries to be tested but only the maximum: 1,400. We expect that the actual numbers of registries tested should be close to the maximum.

It’s a positive sign for applicants, but there are obviously some big unknowns in the process, most notably Governmental Advisory Committee interventions, which are a little under a week away.
On the negative side, ICANN seems to be digging its heels in on the number of pre-delegation tests that will be required, despite recent requests from applicants to streamline the process:

Question 17: Is it possible to execute a single test per Back-End Registry Service Provider (as this would limit the requirement to about 80 such tests)?
The AGB [Applicant Guidebook] specifies one Pre-Delegation Test per Registry Operator (contracted party to ICANN).

This appears to mean that multiple applications using Verisign or Afilias, for example, as their back-ends will have to be individually tested, despite possible duplicative work.

Melbourne IT scales back HARM proposal

Melbourne IT has published a revised, less-complicated version of its High At-Risk Marks (HARM) proposal for protecting famous brands in the new gTLD program.
The new version throws more than a few bones to trademark lawyers, most of whom rejected many aspects of the original proposal at a meeting in Washington DC this September.
It’s a lot closer to the eight-point wish-list published jointly by the Intellectual Property Constituency and Business Constituency last month.
HARM envisions a two-tier set of trademark rights protection mechanisms in new gTLDs, with the super-famous brands that get cybersquatted and phished on a regular basis enjoying greater privileges.
Companies that could prove their trademarks were subject to regular abuse would, for example, benefit from a perpetual Trademark Claims notification service on “brand+keyword” domains.
The new version would lower the bar for inclusion on the list.
The first HARM said trademarks should be registered on five continents, but the new version reduces that to a single registration, provided that the jurisdiction does substantive review.
A provision to only extend the protection to five-year-old marks has also been removed, and the number of UDRP wins required to prove abuse has also been reduced from five to one.
I’ve previously expressed my fondness for the idea of using UDRP decisions to gauge the risk profile of a trademark, but it was recently pointed out to me that it may incentivize mark holders to pay people to cybersquat their marks, in order to win slam-dunk UDRPs and thus benefit from better RPMs, which makes me less fond of it.
Even if such skullduggery is an outside risk, I think a single UDRP win may be too low a bar, given the number of dubious decisions produced by panelists in the past.
The revised HARM would still exclude dictionary words from the special protections (as the paper points out, Apple and Gap would not be covered). The proposal states:

Melbourne IT believes it will be difficult to get consensus in the ICANN community that this mechanism should apply to all trademark owners, most of whom do not suffer any trademark abuse. Many trademarks also relate to generic dictionary words that would be inappropriate to block across all gTLDs.

The original HARM paper was put forth as compromise, designed to help prevent or mitigate the effects of most cybersquatting, while being slightly more palatable to registries and registrars than the usual all-or-nothing demands coming from trademark lawyers.
While not particularly elegant, most of its recommendations were found wanting by the ICANN community, which is as bitterly divided as always on the need for stronger rights protection mechanisms.
The IPC and BC did adopt some of its ideas in their recent joint statement on enhanced RPMs, including the idea that frequently squatted names should get better protection, but rejected many more of the Melbourne-proposed criteria for inclusion on the list.
Meanwhile, many registrars shook their heads, muttering something about cost, and new gTLD applicants staunchly rejected the ideas, based on the mistaken notion that paying their $185,000 has rendered the Applicant Guidebook immutable.
Read the new Melbourne IT paper here (pdf).

Tucows abandoned two new gTLD bids

Tucows originally applied for six new gTLDs but withdrew two of the applications, it emerged yesterday.
During a conference call with analysts, announcing the company’s third-quarter financial results, CEO Elliot Noss said that Tucows’ cash-flow statement had benefited from a $370,000 ICANN refund.
That works out to two full $185,000 refunds, meaning the applications were withdrawn before June’s Big Reveal.
The fact that the money was not recorded until the third quarter is likely due to the delays ICANN subjects applicants to when they request refunds.
Tucows, via a subsidary, has live gTLD bids for group, .marketing, .media and .online, all of which are contested.
Noss reiterated during the earnings call that he does not expect the company to see serious revenue from new gTLDs until 2014, though he speculated that some uncontested geographic gTLDs may start contributing the the second half of 2013.

ICANN, Verisign and NTIA “ready for 100 new gTLDs per week”

The three main entities responsible for managing the domain name system’s root zone have confirmed that they’re ready to add 100 or more new gTLDs to the internet every week.
In a statement, (pdf), ICANN, Verisign and the US National Telecommunications & Information Administration jointly said:

Based on current staffing levels and enhancements that are currently underway to the [Root Zone Management] system, the Root Zone Partners are able to process at least 100 new TLDs per week and will commit the necessary resources to meet all root zone management volume increases associated with the new gTLD program.

The letter was sent in response to a request from ICANN’s Security and Stability Advisory Committee, which asked in July whether ICANN, Verisign and the NTIA were ready for the new gTLD load.
The three-party Root Zone Management procedure used to add TLDs or update existing ones is getting more automation, which is expected to streamline the process.

Trademark Clearinghouse “breakthrough” at private Brussels meeting

ICANN’s various stakeholder groups reached a “breakthrough” agreement on the Trademark Clearinghouse for new gTLDs, according to attendees at a closed-doors meeting last week.
The meeting in Brussels evidently saw attendance from members of the Business Constituency and Intellectual Property Constituency, in addition to the registries and registrars that have been involved in the development of the TMCH implementation model to date.
It was a discussion of nitty-gritty implementation details, according to attendees, rather than reopening the policy discussion on matters such as the mandatory Trademark Claims service period.
Crucially, ICANN appears to have dropped its strong objection to a community-developed proposal that would put the TMCH in the “critical path” for domain registrations.
The community proposal requires a centralized Clearinghouse serving Trademark Claims notices live rather than in a batch fashion, meaning up-time would be paramount.
Senior ICANN executives including chief strategy officer Kurt Pritz were adamant that this model would create an unacceptable single point of failure for the new gTLD program.
But CEO Fadi Chehade, who in Toronto last month appeared to disagree with Pritz, does not appear to have shared these concerns to the same deal-breaking extent.
In a blog post reviewing the meeting’s conclusions last night, Chehade wrote that the community has settled on a “hybrid” solution:

Participants reviewed the features of possible centralized and decentralized systems, and agreed to support a “hybrid” system for Trademark Claims. In this system, a file of domain name labels derived from the trademarks recorded in the Clearinghouse (and hence subject to a Claims Notice) would be distributed to all registries and updated on a regular basis, and a live query system would be used to retrieve the detailed data from the Clearinghouse when necessary to display the Claims Notice to a prospective registrant.

This description appears to closely match the community proposal (pdf) developed by the registries.
ARI Registry Services CTO Chris Wright, one of the key architects of the community TMCH proposal, made no mention of a “hybrid” solution in his update following the Brussels meeting.
According to Wright, “ICANN has tentatively agreed to proceed with the community-developed Trademark Clearinghouse”.
The meeting also concluded that there’s no way to provide blanket privacy protection for trademark data under Trademark Claims, something that has been worrying trademark holders for a while.
At a session in Toronto last month registries observed that the whole point of Trademark Claims is to provide information about trademarks to potential registrants.
That means it can be mined in bulk, and there’s not a heck of a lot registries can do to prevent that even with technical solutions such as throttling access.
Chehade blogged:

There was discussion on implementing an appropriate framework for access and use of the data. The group considered whether measures were necessary specifically to address potential mining of the Clearinghouse database for purposes other than to support the rights protection mechanisms. Given that the Trademark Clearinghouse is designed to provide trademark data for particular purposes, there was agreement that most controls would be ineffective in attempting to control data elements once provided to other parties.

So, how much community support do the Brussels agreements have?
The meeting was not webcast and there does not appear to be a recording or transcript, so it’s difficult to know for sure who was there, what was discussed or what conclusions were reached.
Concerns were expressed by members of the Non-Commercial Stakeholders Group, as well as the Internet Commerce Association, about the fact that ICANN did not widely publicize the meeting, which was first reported in an ICA blog post last week.
The ICA’s Phil Corwin also questioned whether key members of the IPC and BC — based on the US Eastern seaboard — would be able to attend due to Hurricane Sandy’s impact on air travel.
While there seems to be a feeling that solid progress on the Clearinghouse is definitely a positive development for the new gTLD program, the fact that the consensus was apparently reached behind closed doors does not appear to be in lockstep with Chehade’s commitment to increase transparency at ICANN.