ICANN’s top DC lobbyist gets consumer safeguards role

ICANN has named veteran staffer Jamie Hedlund as its new senior VP for contractual compliance and consumer safeguards.
It’s a new executive team role, created by the departure of chief contract compliance officer Allen Grogan. Grogan announced his intention to leave ICANN last May, and has been working there part-time since August.
The “consumer safeguards” part of the job description is new.
ICANN first said it planned to hire such a person in late 2014, but the position was never filled, despite frequent poking by anti-spam activists.
Now it appears that the two roles — compliance and consumer safeguards — have been combined.
This makes sense, give that ICANN has no power to safeguard consumers other than the enforcement of its contracts with registries and registrars.
From the outside, it does not immediately strike me as an obvious move for Hedlund.
While his job title has changed regularly during his six or so years at ICANN, he’s mainly known as the organization’s only in-house Washington DC government lobbyist.
He played a key role in the recent IANA transition, which saw the US government sever its formal oversight ties with ICANN.
His bio shows no obvious experience in consumer protection roles.
His replacement in the government relations role is arguably just as surprising — Duncan Burns, a veteran PR man who will keep his current job title of senior VP of global communications.
The appointments seem to indicate that lobbying the US government is not as critical to ICANN in the post-transition world, and that institutional experience in the rarefied world of ICANN is a key qualifier for senior positions.

ICANN terminates penis pill pimp registrar

ICANN is to terminate the contract of a Chinese registrar linked to dodgy pharmaceuticals web sites and other malfeasance.
Nanjing Imperiosus Technology Co, which does business as DomainersChoice.com, has been told it will lose its registrar accreditation February 3.
ICANN said in the termination notice that the company had failed to keep records related to abuse reports, failed to validate Whois records, and failed to provide ICANN with registration records, all in breach of the Registrar Accreditation Agreement.
The breaches related to complaints filed by illegal pharmacy watchdog LegitScript last September, I believe.
DomainersChoice and its CEO Stefan Hansmann were listed in Whois as the owners of potentially hundreds of domains that were being used to sell medicines for conditions ranging from heart disease to erectile dysfunction.
The domains 5mg-cialis20mg.com, acheterdutadalafil.com, viagra-100mgbestprice.net and 100mgviagralowestprice.net were among those apparently owned by the registrar.
According to LegitScript, thousands of DomainersChoice domains were “rogue internet pharmacies”.
The registrar has also been linked by security researchers to mass typosquatting campaigns.
The company’s web site even has a typo generator. While one could argue such tools are also useful to brand owners, DomainersChoice’s name suggests it’s geared towards domainers, not brands.
DomainersChoice had about 27,000 domains under management at the last count, which ICANN will now migrate to another registrar.
It’s not known how many of those were self-registered domains and how many were being used nefariously, but LegitScript CEO John Horton estimated (pdf) at least 2,300 dodgy pharma sites used the registrar.

Security experts say ICANN should address collisions before approving more new TLDs

ICANN’s Security and Stability Advisory Committee has told ICANN it needs to do more to address the problem of name collisions before it approves any more new gTLDs.
In its latest advisory (pdf), published just before Christmas, SSAC says ICANN is not doing enough to coordinate with other technical bodies that are asserting authority over “special use” TlDs.
The SAC090 paper appears to be an attempt to get ICANN to further formalize its relationship with the Internet Engineering Task Force as it pertains to reserved TLDs:

The SSAC recommends that the ICANN Board of Directors take appropriate steps to establish definitive and unambiguous criteria for determining whether or not a syntactically valid domain name label could be a top-level domain name in the global DNS.
…
Pursuant to its finding that lack of adequate coordination among the activities of different groups contributes to domain namespace instability, the SSAC recommends that the ICANN Board of Directors establish effective means of collaboration on these issues with relevant groups outside of ICANN, including the IETF.

The paper speaks to at least two ongoing debates.
First, should ICANN approve .home and .corp?
These two would-be gTLDs were applied for by multiple parties in 2012 but have been on hold since August 2013 following an independent report into name collisions.
Names collisions are generally cases in which ICANN delegates a TLD to the public DNS that is already broadly used on private networks. This clash can result in the leakage of private data.
.home and .corp are by a considerable margin the two strings most likely to be affected by this problem, with .mail also seeing substantial volume.
But in recent months .home and .corp applicants have started to put pressure on ICANN to resolve the issue and release their applications from limbo.
The second incident the SSAC paper speaks to is the reservation in 2015 of .onion
If you’re using a browser on the privacy-enhancing Tor network, .onion domains appear to you to work exactly the same as domains in any other gTLDs, but under the hood they don’t use the public ICANN-overseen DNS.
The IETF gave .onion status as a “Special Use Domain“, in order to prevent future collisions, which caused ICANN to give it the same restricted status as .example, .localhost and .test.
But there was quite a lot of hand-wringing within the IETF before this status was granted, with some worrying that the organization was stepping on ICANN’s authority.
The SSAC paper appears to be designed at least partially to encourage ICANN to figure out how much it should take its lead from the IETF in this respect. It asks:

The IETF is an example of a group outside of ICANN that maintains a list of “special use” names. What should ICANN’s response be to groups outside of ICANN that assert standing for their list of special names?

For members of the new gTLD industry, the SSAC paper may be of particular importance because it raises the possibility of delays to subsequent rounds of the program if ICANN does not spell out more formally how it handles special use TLDs.
“The SSAC recommends that ICANN complete this work before making any decision to add new TLD names to the global DNS,” it says.

.africa could go live after court refuses injunction

DotConnectAfrica’s attempt to have ICANN legally blocked from delegating the .africa gTLD to rival applicant ZACR has been denied.
The ruling by a Los Angeles court, following a December 22 hearing, means ICANN could put .africa in the root, under ZACR’s control, even before the case comes to trial.
A court document (pdf) states:

The plaintiff is seeking to enjoin defendant Internet Corporation for Assigned Names and Numbers (ICANN) from issuing the .Africa generic top level domain (gTLD) until this case has been resolved…
The plaintiff’s motion for the imposition of a Preliminary Injunction is denied, based on the reasoning expressed in the oral and written arguments of defense counsel.

ICANN was just days away from delegating .africa last April when it was hit by a shock preliminary injunction by a California judge who later admitted he hadn’t fully understood the case.
My understanding is that the latest ruling means ICANN may no longer be subject to that injunction, but ICANN was off for the Christmas holidays last week and unable to comment.
“Sanity prevails and dotAfrica is now one (big) step closer to becoming a reality!” ZACR executive director Neil Dundas wrote on Facebook. He declined to comment further.
Even if ICANN no longer has its hands tied legally, it may decide to wait until the trial is over before delegating .africa anyway.
But its lawyers had argued that there was no need for an injunction, saying that .africa could be re-delegated to DCA should ICANN lose at trial.
DCA case centers on its claims that ICANN treated it unfairly, breaking the terms of the Applicant Guidebook, by awarding .africa to ZACR.
ZACR has support from African governments, as required by the Guidebook, whereas DCA does not.
But DCA argues that a long-since revoked support letter from the African Union should still count, based on the well-known principle of jurisprudence the playground “no take-backs”.
The parties are due to return to court January 23 to agree upon dates for the trial.

URS comes to .mobi as ICANN offers Afilias lower fees

Afilias’ .mobi is to become the latest of the pre-2012 gTLDs to agree to adopt the Uniform Rapid Suspension policy in exchange for lower ICANN fees.
Its Registry Agreement is up for renewal, and Afilias and ICANN have come to similar terms to .jobs, .travel, .cat, .pro and .xxx.
Afilias has agreed to take on many of the provisions of the standard new gTLD RA that originally did not apply to gTLDs approved in the 2000 and 2003 rounds, including the URS.
In exchange, its fixed registry fees will go down from $50,000 a year to $25,000 a year and the original price-linked variable fee of $0.15 to $0.75 per transaction will be replaced with the industry standard $0.25.
It’s peanuts really, given that .mobi still has about 690,000 domains, but Afilias is getting other concessions too.
Notably, the ludicrous mirage that .mobi was a “Sponsored” gTLD serving a specific restricted community (users of mobile telephones, really) rather than an obvious gaming of the 2003-round application rules, looks like it’s set to evaporate.
Appendix S to the current RA is not being carried over, ICANN said, so .mobi will not become a “Community” gTLD, with all the attendant restrictions that would have entailed.
Instead, Afilias has simply agreed to the absolute basic set of Public Interest Commitments that apply to all 2012 new gTLDs. Text that would have committed the registry to abide by the promises made in its gTLD application have been removed.
But the change likely to get the most hackles up is the inclusion of URS in the proposed new contract.
URS is an anti-cybserquatting measure that enables trademark owners to shut down infringing domains, without taking ownership, more quickly and cheaply than the UDRP.
It’s obligatory for all 2012-round gTLDs, and five of the pre-2012 registries have also agreed to adopt it during their contract renewal talks with ICANN.
Most recently, ICM Registry agreed to URS in exchange for much deeper cuts in its ICANN fees in .xxx.
In recent days, ICANN published its report into the public comments on the .xxx renewal, summarizing some predictably irate feedback.
Domainer group the Internet Commerce Association, which is concerned that URS will one day be forced upon .com and .net, had a .xxx comment that seems particularly pertinent to the .mobi news:

Given the history of flimsy and self-serving justifications by [Global Domains Division] staff and the ICANN Board for similar actions taken in 2015, we are under no illusion that this comment letter will likely be successful in effecting removal of the URS and other new gTLD RA provisions from the revised .XXX RA. Nonetheless, we strenuously object to this GDD action that intrudes upon and debases ICANN’s legitimate policymaking process, and urge the GDD and Board to reconsider their positions, and to ensure that GDD staff ceases and desists from taking similar action in the context of future RA renewals and revisions until the RPM Review WG renders the community’s judgment as to whether the URS and other new gTLD RPMs should become Consensus Policy and such recommendation is reviewed by GNSO Council and the ICANN Board.

The Intellectual Property Constituency of the GNSO, conversely, broadly welcomed the addition of more rights protection mechanisms to .xxx.
The Non-Commercial Stakeholder Group, meanwhile, expressed concern that whenever ICANN negotiates a non-consensus policy into a contract it negates and discourages all the work done by the volunteer community.
You can read the summary of the .xxx comments, along with ICANN staff’s reasons for ignoring them, here (pdf).
The .mobi proposed amendments are also now open for public comment.
Any lawyers wishing to rack up a few billable hours railing against a fait accompli can do so here.

Registrars off the hook for silly ICANN transfer policy

Domain name registrars have been assured that ICANN Compliance will not pursue them for failing to implement the new Transfer Policy on privacy-protected names.
As we reported late November, the new policy requires registrars to send out “change of registrant” confirmation emails whenever certain fields in the Whois are changed, regardless of whether the registrant has actually changed.
The GNSO Council pointed out to ICANN a number of unforeseen flaws in the policy, saying that vulnerable registrants privacy could be at risk in certain edge cases.
They also pointed out that the confirmation emails could be triggered, with not action by the registrant, when privacy services automatically cycle proxy email addresses in the Whois.
This appears to have already happened with at least one registrar that wasn’t paying attention.
But ICANN chair Steve Crocker told the GNSO Council chair last week that ICANN staff have been instructed to ignore violations of the new policy, which came into effect December 1, in cases involving privacy-protected domains (pdf).
It’s a temporary measure until the ICANN board decides whether or not to defer the issue to the GNSO working group currently looking at policies specifically for privacy and proxy services.

Mitsubishi pulls plug on dot-brand gTLD

Japanese conglomerate Mitsubishi has told ICANN it no longer wishes to operate one of its dot-brand gTLDs.
The company has filed a termination notice covering its .mtpc domain, which stands for Mitsubishi Tanabe Pharma Corporation.
The gTLD was delegated in February 2015, but Mitsubishi has never put it to use.
Registry reports show only two names ever appeared in the .mtpc space.
It’s the 19th gTLD from the 2012 round to voluntarily self-terminate — or to allow ICANN to terminate it — after signing a Registry Agreement.
All terminated gTLDs so far have been dot-brands.
Mitsubishi also owns .mitsubishi. That dot-brand appeared earlier this year but also has not yet been put to use.

Pheenix adds 300 more registrars to drop-catch arsenal

The domain drop-catching arms race is heating up, with budget player Pheenix this week acquiring 300 more registrar accreditations from ICANN.
According to DI records, the company now has almost 500 registrar accreditations in its family.
More accreditations means more registry connections with which to attempt to acquire expired domains as they return to the available pool.
It also means that Pheenix’s dropnet (a word I just made up that sounds a bit like “botnet” in a pathetic attempt to coin a term for once in my career) is now a bit bigger than that of Web.com, the registrar pool behind Namejet and SnapNames.
It’s still a long way behind TurnCommerce, owner of DropCatch, which two weeks ago added a whopping 500 new accreditations, bringing its total to over 1,250.
An extra 300 accreditations would have cost Pheenix over $1 million in up-front ICANN fees and will incur ongoing fixed annual fees in excess of $1.2 million.

After Zika threat passes, ICANN confirms return to Puerto Rico

ICANN will hold its first public meeting of 2018 in San Juan, Puerto Rico, which was originally supposed to the venue for this October’s meeting.
ICANN moved ICANN 57 from San Juan to Hyderabad, India in May, at the height of the scare about the Zika virus.
Zika is spread by mosquitoes and sex and can cause horrible birth defects. An epidemic, beginning in 2015, saw thousands affected in the Americas and South-East Asia.
Puerto Rico was one of the affected regions. At the time of the ICANN postponement, numerous government travel warnings were in effect.
The World Health Organization announced last month that the epidemic is over.
It was always understood that Puerto Rico had been merely postponed rather than permanently canceled, and ICANN’s board of directors this week resolved to hold the March 2018 meeting — ICANN 61 — there.

Survey says most Whois records “accurate”

Ninety-seven percent of Whois records contain working email addresses and/or phone numbers, according to the results of an ongoing ICANN survey.
The organization yesterday published the second of its now-biannual WHOIS Accuracy Reporting System reports, a weighty document stuffed with facts and figures about the reliability of Whois records.
It found, not for the first time, that the vast majority of Whois records are not overtly fake.
Email addresses and phone numbers found there almost always work, the survey found, and postal addresses for the most part appear to be real postal addresses.
The survey used a sample of 12,000 domains over 664 gTLDs. It tested for two types of accuracy: “syntactical” and “operability”.
Syntactical testing just checks, for example, whether the email address has an @ symbol in it and whether phone numbers have the correct number of digits.
Operability testing goes further, actually phoning and emailing the Whois contacts to see if the calls connect and emails don’t bounce back.
For postal addresses, the survey uses third-party software to see whether the address actually exists. No letters are sent.
The latest survey found that 97% of Whois records contain at least one working phone number or email address, “which implies that nearly all records contain information that can be used to establish immediate contact.”
If you’re being more strict about how accurate you want your records, the number plummets dramatically.
Only 65% of records had operable phone, email and postal contact info in each of the registrant, administrative and technical contact fields.
Regionally, fully accurate Whois was up to 77% in North America but as low as 49.5% in Africa.
So it’s not great news if Whois accuracy is your bugbear.
Also, the survey does not purport to verify that the owners of the contact information are in fact the true registrants, only that the information is not missing, fake or terminally out-of-date.
A Whois record containing somebody else’s address and phone number and a throwaway webmail address would be considered “accurate” for the survey’s purposes.
The 54-page survey can be found over here.