The new gTLD .food went live in the DNS on Friday, but nobody except the registry will be able to register domains there.
In what I would argue is one of the new gTLD program’s biggest failures, .food will be a dot-brand, closed to all except the “brand” owner.
The registry is Lifestyle Domain Holdings, a subsidiary of US media company Scripps Networks.
Scripps runs the Food Network TV station in the States and the site Food.com. It has a trademark on the word “Food”.
Its registry agreement for .food, signed back in April, includes Specification 13, which allows registries to restrict all the second-level domains to themselves and their affiliates.
So food producers, restaurants, chefs and the like will never be able to use .food for their web sites.
ICANN signed the contract with Scripps despite objections from several entities including the Australian government, which warned “restricting common generic strings, such as .food, for the exclusive use of a single entity could have a negative impact on competition”.
Under ICANN rules hastily cobbled together after outrage over so-called “closed generics”, a registry cannot run as a dot-brand a gTLD that is:
a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.
Almost all applications flagged as closed generics were subsequently amended to make them restricted but not brand-exclusive. Scripps was the major hold-out.
The loophole that allowed .food to stay in exclusive hands appears to be that Scripps’ trademark on “Food” covers television, rather than food.
If .food winds up publishing content about food, such as recipes and healthy eating advice, I’d argue that it would go against the spirit of the rules on closed generics.
It would be a bit like Apple getting .apple as a Spec 13 dot-brand and then using the gTLD to publish content about the fruit rather than computers.
No sites are currently live in .food.
GMO Registry is to offer .shop domain registrants a free one-year SSL certificate with every purchase.
The company said yesterday that the deal, made via sister certificate company GMO GlobalSign, should be in place by the end of the month.
The certs on offer appear to be the of low-end “Domain Validation” variety.
Nevertheless, GlobalSign usually sells them for over $150 per year, many times more expensive than .shop domains themselves.
Popular registrars are currently selling .shop names from $10 to $25.
There are about 90,000 domains in .shop’s zone file today.
That’s a goodish volume by new gTLD standards, but probably not good enough to help GMO recoup the $41.5 million it paid for .shop at auction any time soon.
Upsell opportunities such as the SSL offer, assuming they get any uptake, may help accelerate its path to breakeven.
New gTLD registry operators have been given the right to start selling two-letter domains that match country codes.
Potentially thousands of names could start being released next year, resulting in a windfall for registries and possible opportunities for investors.
Some governments, however, appear to be unhappy with the move and how ICANN’s board of directors reached its decision.
The ICANN board yesterday passed a resolution that will unblock all two-letter domains that match country codes appearing on the ISO 3166 list, most of which are also ccTLDs.
While the resolution gives some protection to governments worried about abuse of “their” strings, it’s been watered down to virtually nothing.
In the first draft of the rules, published in July, ICANN said registries “must” offer an “Exclusive Availability Pre-registration Period” — a kind of mini-sunrise period limited to governments and ccTLD operators.
In the version approved by ICANN yesterday, the word “must” has been replaced by “may” and the word “voluntary” has been added.
In other words, registries won’t have to give any special privileges to governments when they start selling two-character names.
They will, however, have to get registrants to agree that they won’t pass themselves off as having affiliations with the relevant government. It looks like registries probably could get away with simply adding a paragraph to their terms of service to satisfy this requirement.
Registries will also have to “take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain.”
This too is worded vaguely enough that it could wind up being worthless to governments, many of which are worried about domains matching their ccTLDs being passed off as government-approved.
The Governmental Advisory Committee is split on how worrisome this kind of thing is.
For examples, governments such as Spain and Italy have fought for the right to get to pre-approve the release of “es” and “it” domains, whereas the governments of the US and UK really could not care less.
The most-recent formal GAC advice on the subject, coming out of the July meeting in Helsinki, merely said ICANN should:
urge the relevant Registry or the Registrar to engage with the relevant GAC members when a risk is identified in order to come to an agreement on how to manage it or to have a third-party assessment of the situation if the name is already registered
“It is our belief that that our resolution is consistent with GAC advice,” outgoing ICANN board member Bruce Tonkin said yesterday, noting that nobody can claim exclusive rights over any string, regardless of length.
Before and after the resolution passed, the GAC expressed “serious concern” that the board had not formally responded to the Helsinki communique.
In its Hyderabad communique, issued after yesterday’s vote, the GAC advised the board to:
- Clearly indicate whether the actions taken by the Board as referred to in the resolution adopted on 8 November 2016 are fully consistent with the GAC advice given in the Helsinki Communiqué.
- Always communicate in future the position of the Board regarding GAC advice on any matter in due time before adopting any measure directly related to that advice.
ICANN staff are now tasked with coming up with a way to implement the two-character release.
My sense is that some kind of amendment to Registry Agreements might be required, so we’re probably looking at months before we start seeing two-letter domains being released.
Fears that the domain name industry is becoming a stooge for “shadow regulation” of web content were raised, and greeted very skeptically, over the weekend at ICANN 57.
Attendees yesterday heard concerns from non-commercial stakeholders, notably the Electronic Frontier Foundation, that deals such as Donuts’ content-policing agreement with the US movie industry amount to regulation “by the back door”.
But the EFF, conspicuously absent from substantial participation in the ICANN community for many years, found itself walking into the lion’s den. Its worries were largely pooh-poohed by most of the rest of the community.
He was not alone. The ICANN board and later the community at large heard support for the EFF’s views from other Non-Commercial User Constituency members, one of whom compared what’s going on to aborted US legislation SOPA, the Stop Online Piracy Act.
“Regulation of content through the DNS system, through ICANN institutions and through contracted parties is of great concern and I think should be of great concern to all of us here,” Stoltz said.
He talked about a “bright line” between making policies related to domain names and policies related to content.
“I hope that the bright line between names and content is maintained because I think once we get past it, there may be no other bright line,” he said.
“If we allow in copyright enforcement, if we allow in enforcement of professional or business licensing as a criterion for owning a domain name, it’s going to be very hard to hold that line,” he said.
ICANN has long maintained, though with varying degrees of vigor over the years, that it does not regulate content.
Chair Steve Crocker said yesterday: “It’s always been the case, from the inception. It’s now baked in deeply into the mission statement. We don’t police content. That’s not our job.”
That kind of statement became more fervent last year, as concerns started to be raised about ICANN’s powers over the internet in light of the US government’s decision to give up its unique ICANN oversight powers.
Now, a month after the IANA transition was finalized, ICANN has new bylaws that for the first time state prominently that ICANN is not the content cops.
Page one of the massive new ICANN bylaws says:
ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet’s unique identifiers or the content that such services carry or provide
It’s pretty explicit, but there’s a catch.
A “grandfather” clause immediately follows, which states that registries and registrars are not allowed to start challenging the terms of their existing contracts on the basis that they dabble too much with content regulation.
That’s mainly because new gTLD Registry Agreements all include Public Interest Commitments, which in many cases do actually give ICANN contractual authority over the content of web sites.
Content-related PICs are most prominent in “Community” gTLDs.
In the PICs for Japanese city gTLD .osaka, for example, the registry promises that “pornographic, vulgar and highly objectionable content” will be “adequately monitored and removed from the namespace”.
While ICANN does not actively go out looking for .osaka porn, if porn did start showing up in .osaka and the registry does not suspend the domains, it would be in breach of its RA and could lose its contract.
That PIC was voluntarily adopted by the .osaka registry and does not apply to other gTLDs, but it is binding.
So in a roundabout kind of way, ICANN does regulate content, in certain narrow circumstances.
Some NCUC members think this is a “loophole”.
Another back door they think could be abused are the bilateral “trusted notifier” relationships between registries and third parties such as the movie, music and pharmaceutical industries.
Donuts said it has suspended a dozen domains — sites that were TLD-hopping to evade suspension — since the policy came into force.
EFF’s Stoltz calls this kind of thing “shadow regulation”.
“Shadow regulation to us is the regulation of content… through private agreements or through unaccountable means that were not developed through the bottom-up process or through a democratic process,” he told the ICANN board yesterday.
While the EFF and NCUC thinks this is a cause for concern, they picked up little support from elsewhere in the community.
Speakers from registries, registrars, senior ICANN staff, intellectual property and business interests all seemed to think it was no big deal.
In a different session on the same topic later in the day, outgoing ICANN head of compliance Allen Grogan addressed these kinds of deals. He said:
From ICANN’s point of view, if there are agreements that are entered into between two private parties, one of whom happens to be a registry or a registrar, I don’t see that ICANN has any role to play in deciding what kinds of agreements those parties can enter into. That clearly is outside the scope of our mission and remit.
We can’t compel a registrar or a registry to even tell us what those agreements are. They’re free to enter into whatever contracts they want to enter into.
To the extent that they become embodied in the contracts as PICs, that may be a different question, or to the extent that the agreements violate those contracts or violate consensus policies, that may be a different question.
But if a registrar or registry decides to enter into an agreement to trust the MPAA or law enforcement or anyone else in deciding what actions to take, I think they’re free to do that and it would be far beyond the scope of ICANN’s power or authority to do anything about that.
In the same session, Donuts VP Jon Nevett cast doubt on the idea that there is an uncrossable “bright line” between domains and content by pointing out that the MPAA deal is not dissimilar to registries’ relationships with the bodies that monitor online child abuse material.
“We have someone that’s an expert in this industry that we have a relationship with saying there is child imagery abuse going on in a name, we’re not going to make that victim go get a court order,” he said.
Steve DelBianco of the NetChoice Coalition, a member of the Business Constituency, had similar doubts.
“Mitch [Stoltz] cited as an example that UK internet service providers were blocking child porn and since that might be cited as an example for trademark and copyright that we should, therefore, not block child porn at all,” he said. “I can’t conceive that’s really what EFF is thinking.”
Nevett gave a “real-life example” of a rape.[tld] domain that was registered in a Donuts gTLD.
“[The site] was a how-to guide. Talk about horrific,” he said. “We got a complaint. I’m not going to wait till someone goes and gets a court order. We’re a private company and we agreed to suspend that name immediately and that’s fine. There was no due process. And I’m cool with that because that was the right thing to do.”
“Just like a restaurant could determine that they don’t want people with shorts and flip-flops in the restaurant, we don’t want illegal behavior and if they want to move somewhere else, let them move somewhere else,” he said.
In alleged copyright infringement cases, registrants get the chance to respond before their names are suspended, he said.
Stoltz argued that the Donuts-MPAA deal had been immediately held up, when it was announced back in February, as a model that the entire industry should be following, which was dangerous.
“If everyone is subject to the same policies, then they are effectively laws and that’s effectively law-making by other means,” he said.
He and other NCUC members are also worried about the Domain Name Association’s Healthy Domains Initiative, which is working on voluntary best practices governing when registries and registrars should suspend domain names.
Lawyer Kathy Kleiman of the NCUC said the HDI was basically “SOPA behind closed doors”.
SOPA was the hugely controversial proposed US federal legislation that would have expanded law enforcement powers to suspend domains in cases of alleged copyright infringement.
Stoltz and others said that the HDI appeared to be operating under ICANN’s “umbrella”, giving it an air of having multistakeholder legitimacy, pointing out that the DNA has sessions scheduled on the official ICANN 57 agenda and “on ICANN’s dime”.
DNA members disagreed with that characterization.
It seems to me that the EFF’s arguments are very much of the “slippery slope” variety. While that may be considered a logical fallacy, it does not mean that its concerns are not valid.
But if there was a ever a “bright line” between domain policy and content regulation, it was traversed many years ago.
The EFF and supporters perhaps should just acknowledge that what they’re really concerned about is copyright owners abusing their powers, and target that problem instead.
The line has moved.
Governments are toying with the idea of asking ICANN for greater powers over gTLDs that match their geographic features.
The names of rivers, mountains, forests and towns could be protected under ideas bandied around at the ICANN 57 meeting in India today.
The Governmental Advisory Committee held a session this morning to discuss expanding the list of strings that already enjoy extra ICANN protections on grounds of geography.
In the 2012 application round, gTLDs matching the names or ISO acronyms of countries were banned outright.
For capital city names and non-capital names where the gTLD was meant to represent the city in question, government approval was required.
For regions on the ISO 3166 list, formal government non-objection was required whether or not the gTLD was intended to represent the region.
That led to gTLDs such as .tata, a dot-brand for Tata Group, being held up indefinitely because it matches the name of a small region of Morocco.
One applicant wound up agreeing to fund a school to the tune of $100,000 in order to get Montenegro’s support for .bar.
But other names were not protected.
Notably, the string “Amazon” was not on any of the protected lists, largely because while it’s a river and a forest it doesn’t match the name of a formal administrative region of any country.
While GAC objections ultimately killed off Amazon’s bid for .amazon (at least for now), the GAC wants to close the Amazon loophole in time for the next new gTLD application round.
The GAC basically is thinking about the power to write its own list of protected terms. It would build on the existing list to also encompass names of “geographic significance”.
GAC members would be able to submit names to the list; applicants for those names would then require non-objection letters from the relevant government(s).
Some governments, including the UK and Peru, expressed concern that “geographic significance” is a little vague.
Truly, without a narrow definition of “significance” it could turn out to be a bloody big list. The UK alone has over 48,000 towns, not to mention all the named forests, rivers and such.
Peru, one of the nations that had beef with Amazon, said it intended to send ICANN a list of all the geographic names it wants protecting, regardless of whether the GAC decides to create a new list.
Other GAC members, including Iran and Denmark, pressed how important it was for the GAC to coordinate with other parts of the ICANN community, mainly the GNSO, on geo names, to avoid overlap and conflict further down the line.
The GAC has a working group looking at the issue. It hopes to have something to recommend to the ICANN board by the Copenhagen meeting next March.