Whois policy group closes down in face of GDPR

An ICANN working group devoted to crafting Whois policy has closed down “until further notice” in light of the EU General Data Protection Regulation.
The Registration Data Service Policy Development Process Working Group will have no more meetings until it receives “guidance from the [ICANN] Board regarding how this WG will be affected by the GDPR compliance efforts”.
That’s according to WG co-chair Chuck Gomes, in an email to the group this morning. The mailing list will remain active to keep members informed of progress, he said.
The group has been tasked with developing “comprehensive Whois reform”.
It’s been working for over two years to attempt to find consensus on changes such as tiered access and data privacy, the latest iteration of fruitless, fractious Whois policy discussions dating back a couple of decades, and had made very little progress.
Recently, it’s also been hit by infighting and, in my opinion, a sense of helplessness in the face of GDPR, the EU privacy law that will take precedence over any policy ICANN comes up with.
Last month, prominent Non-Commercial Stakeholder Group member Stephanie Perrin publicly resigned from the WG, saying it was “fundamentally flawed” and complaining the process was an “antique” that wasn’t sufficiently taking GDPR into account.
As DI has been reporting for the last several months, there’s very little clarity right now about how GDPR will effect ICANN’s Whois policy.
ICANN CEO Goran Marby told us yesterday that he’s “cautiously optimistic” that EU data protection authorities will soon provide some firm guidance on what it means to be GDPR-compliant.
It appears that the RDS group’s fate may also lie in the hands of the DPAs, for now.

1 Comment Tagged: gdpr, ICANN, privacy, rds, whois

Marby ponders emergency powers to avoid fragmented Whois

ICANN could invoke emergency powers in its contracts to prevent Whois becoming “fragmented” after EU privacy laws kick in next month.
That’s a possibility that emerged during a DI interview with ICANN CEO Goran Marby yesterday.
Marby told us that he’s “cautiously optimistic” that European data protection authorities will soon provide clear guidance that will help the domain industry become compliant with the General Data Protection Regulation, which becomes fully effective May 25.
But he said that a lack of such guidance will lead to a situation where different companies provide different levels of public Whois.
“It’s a a high probability that Whois goes fragmented or that Whois will be in a sort of ‘thin’ model in which very little information is collected and very little information is displayed,” he said. “That’s a sort of worst-case scenario.”
I should note that the interview was conducted yesterday before news broke that Afilias has become the first major gTLD registry to announce its Whois output will be essentially thin — eschewing all registrant contact data — from May 25.
Marby has asked European DPAs for two things.
First, guidance on whether its “Cookbook” proposal for a dramatically scaled-back, GDPR-compliant Whois is in fact GDPR-compliant.
Second, an enforcement moratorium while registries and registrars actually go about implementing the Cookbook.
“If we don’t get guidance that’s clear enough, we will see a fragmented Whois. If we get guidance that is clear enough we can work it out,” Marby said.
A moratorium could enable Whois to carry on in its current state, or something close to it, while ICANN goes about creating a new policy that fits with the DPA’s guidance.
If the DPAs refuse a moratorium, we’re looking at a black hole of indeterminate duration during which nobody — not even law enforcement or self-appointed trademark cops — can easily access full Whois records.
“It’s not something I can do anything about, it’s really in the hands of the DPAs,” Marby said. “Remember that it’s the law.”
While ICANN has expended most of its effort to date on creating a model for the public Whois, there’s a parallel effort to create an accreditation program that would enable organizations with “legitimate purposes” to access full, or at least more complete, Whois records.
It’s the IP lawyers that are driving this effort, primarily, terrified that their ability to hunt down cybersquatters and bootleggers will be diminished come May 25.
ICANN has so far resisted calls to endorse the so-called “Cannoli” draft accreditation model, with Marby publicly saying that it needs cross-community support.
But the organization has committed staff support resources to discussion of Cannoli. There’s a new mailing list and there will be a community conference call this coming Friday at 1400 UTC.
Marby said that he shares the worries of the IP community, adding: “If we get the proper guidance from the DPAs, we will know how to sort out the accreditation model.”
He met with the Article 29 Working Party, comprised of DPAs, last week; the group agreed to put Whois on its agenda for its meeting next week, April 10-11.
The fact that it’s up for discussion is what gives Marby his cautious optimism that he will get the guidance he needs.
Assuming the DPAs deliver, ICANN is then in the predicament of having to figure out a way to enforce, via its contracts, a Whois system that is compliant with the DPAs’ interpretation of GDPR.
Usually, this would require a GNSO Policy Development Process leading to a binding Consensus Policy.
But Marby said ICANN’s board of directors has other options, such as what he called an “emergency policy”.
This is a reference, I believe, to the “Temporary Policies” clauses, which can be found in the Registrar Accreditation Agreement and Registry Agreement.
Such policies can be mandated by a super-majority vote of the board, would have to be narrowly tailored to solve the specific problem at hand, and could be in effect no longer than one year.
A temporary policy could be replaced by a compatible, community-created Consensus Policy.
It’s possible that a temporary policy could, for example, force Afilias and others to reverse their plans to switch to thin Whois.
But that’s perhaps getting ahead of ourselves.
Fact is, the advice the DPAs provide following their Article 29 meeting next week is what’s going to define Whois for the foreseeable future.
If the guidance is clear, the ICANN organization and community will have their direction of travel mapped out for them.
If it’s vague, wishy-washy, and non-committal, then it’s likely that only the European Court of Justice will be able to provide clarity. And that would take many years.
And whatever the DPAs say, Marby says it is “highly improbable” that Whois will continue to exist in its current form.
“The GDPR will have an effect on the Whois system. Not everybody will get access to the Whois system. Not everybody will have as easy access as before,” he said.
“That’s not a bug, that’s a feature of the legislation,” he said. “That’s not ICANN’s fault, it’s what the legislator thought when it made this legislation. It is the legislators’ intention to make sure people’s data is handled in a different way going forward, so it will have an effect.”
The community awaits the DPAs’ guidance with baited breath.

17 Comments Tagged: afilias, article 29 working party, dpas, gdpr, ICANN, privacy, whois

ICANN heads to Mar-a-Lago for budget crisis talks

Cash-strapped ICANN has invited select community members to emergency budget talks at the Mar-a-Lago resort in Florida, DI has learned.
The three-day summit next week will address how best to spend the organization’s $138 million annual budget, along with its $236 million auction proceeds war chest and its $80 million of leftover new gTLD application fees.
“Recent public comments have made it clear than many valued ICANN community members have misunderstood our FY19 budget,” CEO Goran Marby said. “I believe a long weekend of intensive discussions at Mar-a-Lago should persuade the community that we’re actually on the right track.”
To encourage participation from an increasingly weary volunteer pool, attendees will be treated to complimentary spa treatments, golfing, and the most beautiful pieces of chocolate cake, he said.
DI has managed to obtain a preliminary agenda for the summit, which can be read here (pdf).
Business-class flights and three nights’ accommodation at the exclusive members club will be covered by ICANN.
Mar-a-Lago, purchased by Donald Trump in the 1980s, is a “six-star” resort in Palm Beach, Florida. It was originally a five-star hotel, until 2004 when Trump purchased the one-star hotel next door and knocked through.
Marby defended the choice of venue, pointing out that the guest list is to be strictly limited to the ICANN board of directors, industry CEOs, and members of the Intellectual Property Constituency.
DI understands that the IPC will be permitted to invite members of the Non-Commercial Stakeholder Group to attend, should they require golf caddies.
To ensure gender diversity, all attendees will be able to bring along their spouses or partners. ICANN will make up any shortfall by hiring decorative females from a pool of Trump litigants.
A small support team of 50 ICANN staffers will also be available to hand out fresh towels, collect empty glasses, and so on.
Remote participation will be available via AOL Instant Messenger.
Chief financial officer Xavier Calvez declined to disclose the cost of the summit, citing privacy concerns caused by “GDPR or something”, but DI understands it is to be accounted for as a line item in ICANN’s Federal lobbying disclosure.
Calvez said ICANN has managed to negotiate “substantial” bulk discounts on the usual $200,000 Mar-a-Lago membership fees and $2,000-a-night room rates.
The cost will also be offset by sponsorship contributions from ICANNwiki and the National Rifle Association, he said.
Registry and registrar CEOs polled by DI this weekend were split on whether they would attend.
“Of course I’m going,” Blacknight CEO Michele Neylon told us by phone from an airport lounge in Kigali.
But .xyz chief Daniel Negari said he would attend only if he can secure sufficient funding for his bus fare to the airport.
Among the cost-cutting proposals on the menu, DI understands, is a request to consolidate all current and future policy working groups into a single, unified WG.
Sources say this would have the added benefit of reducing the annual policy implementation budget to zero dollars between now and, at the earliest, 2045.

17 Comments Tagged: april 1

Registrars will miss GDPR deadline by a mile

Registries and registrars won’t be able to implement ICANN’s proposed overhaul of the Whois system in time for the EU’s General Data Protection Regulation coming into effect.
That’s according to an estimated timetable (pdf) sent by ICANN’s contracted parties to the organization this week.
While they feel confident that some elements of ICANN’s GDPR compliance plan could be in place before May 25 this year, when the law kicks in, they feel that other elements could take many months to design and roll out.
Depending on the detail of the finalized plan, we could be looking at the back end of 2019 before all the pieces have been put in place.
Crucially, the contracted parties warn that designing and rolling out a temporary method for granting Whois access to entities with legitimate interests in the data, such as police and trademark owners, could take a year.
And that’s just the stop-gap, Band-Aid hack that individual registries and registrars would put in place while waiting — “quarters (or possibly years), rather than months” — for a fully centralized ICANN accreditation solution to be put in place.
The outlook looks bleak for those hoping for uninterrupted Whois access, in other words.
But the timetable lists many other sources of potential delay too.
Even just replacing the registrant’s email address with a web form or anonymized forwarding address could take up to four months to put online, the contracted parties say.
Generally speaking, the more the post-GDPR Whois differs from the current model the longer the contracted parties believe it will take to roll out.
Likewise, the more granular the controls on the data, the longer the implementation window.
For example, if ICANN forces registrars to differentiate between legal and natural persons, or between European and non-European registrants, that’s going to add six months to the implementation time and cost a bomb, the letter says.
Anything that messes with EPP, the protocol underpinning all registry-registrar interactions, will add some serious time to the roll-out too, due to the implementation time and the contractual requirement for a 90-day notice period.
The heaviest workload highlighted in the letter is the proposed opt-in system for registrants (such as domain investors) who wish to waive their privacy rights in favor of making themselves more contactable.
The contracted parties reckon this would take nine months if it’s implemented only at the registrar, or up to 15 months if coordination between registries and registrars is required (and that timeline assumes no new EPP extensions are going to be needed).
It’s possible that the estimates in the letter could be exaggerated as part of the contracted parties’ efforts to pressure ICANN to adopt the kind of post-GDPR Whois they want to see.
But even if we assume that is the case, and even if ICANN were to finalize its compliance model tomorrow, there appears to be little chance that it will be fully implemented at all registrars and registries in time for May 25.
The letter notes that the timetable is an estimate and does not apply to all contracted parties.
As I blogged earlier today, ICANN CEO Goran Marby has this week reached out to data protection authorities across the EU for guidance, in a letter that also asks the DPAs for an enforcement moratorium while the industry and community gets its act together.
Late last year, ICANN also committed not to enforce the Whois elements of its contracts when technical breaches are actually related to GDPR compliance.

4 Comments Tagged: gdpr, ICANN, privacy, whois

ICANN chief begs privacy watchdogs for Whois advice

ICANN CEO Goran Marby has written to the data protection authorities of all 28 European Union states, along with the European Data Protection Supervisor, to ask for guidance on how to implement new privacy laws.
Marby also asked the DPAs about the possibility of an enforcement moratorium, to give the domain industry and ICANN more time to formulate their collective response to the General Data Protection Regulation.
GDPR, which aims to give EU citizens more control over their personal data, comes into full effect May 25. Companies that break the rules face fines that could amount to millions of euros.
But ICANN does not yet have a firm plan for bringing the distributed Whois system into compliance with GDPR, and has repeatedly indicated that it needs guidance from European DPAs.
“ICANN and more than a thousand of the domain names registries and registrars are at a critical juncture,” Marby wrote (pdf).
“We need specific guidance from European data protection authorities in order to meet the needs of the global internet stakeholder community, including governments, privacy authorities, law enforcement agencies, intellectual property holders, cybersecurity experts, domain name registries, registrars, registrants and ordinary internet users,” he wrote.
ICANN has already written a proposal — known as the “Cookbook” and sent to DPAs three weeks ago — for how gTLD registrars and registries could comply with GDPR by removing most fields from public Whois records.
But Marby’s letter points out that many ICANN community members think the Cookbook either goes too far or not far enough.
As we reported a week ago, the Governmental Advisory Committee and Intellectual Property Constituency are not convinced ICANN needs to chop quite as much info from the public Whois as it’s currently planning.
But on the flipside, there are privacy advocates who think far less data should be collected on registrants and fundamentally question ICANN’s power to mandate public Whois access in its registry and registrar contracts.
Both sides of the debate are referenced in the letter.
“Guidance from DPAs on ICANN’s plan of action as presented in the Cookbook, and in particular, the areas where there are competing views, is critical as soon as possible, but particularly during the next few weeks,” Marby wrote.
Whether ICANN will get the answers it needs on the timetable it needs them is open to debate.
Many community members expressed skepticism about whether the DPAs’ commitment to the urgency of the issue matches ICANN’s own, during ICANN 61 earlier this month.
There seemed to be little confidence that the DPAs’ responses, should ICANN receive any, will provide the clarity the industry needs.
It may also be bad timing given the unrelated Cambridge Analytica/Facebook scandal, which appears to be consuming the attention of some European DPAs.

2 Comments Tagged: cookbook, dpas, gdpr, ICANN, privacy, whois

Stéphane Van Gelder dies after motorcycle accident

I’m very sad to report that domain name industry veteran and ICANN community leader Stéphane Van Gelder has died. He was 51.
Friends tell me he died today of injuries sustained in a vehicle crash in Switzerland near the Italian border.
According to a local report, he and his wife were hit by a car March 23, while stopped on their motorcycles at a traffic light.
His wife, Julie, was also injured but survived.
Stéphane was a long-time member of the industry, in 1999 co-founding the French registrar Indom, which he sold to Group NBT in 2010.
After Indom, he became an independent consultant, first under the brand Stéphane Van Gelder Consulting, later as Milathan.
He joined new gTLD registry StartingDot in 2014 and saw the company through to its acquisition by Afilias in 2016.
He told us at the time of his rebranding that the name “Milathan” was a “derivative of words in Hindi that mean ‘union’ or ‘meeting’ in the sense of bringing people together”.
It was perhaps an appropriate name, given Stéphane’s record of successful senior leadership positions in the ICANN volunteer community.
Notably, he chaired the GNSO Council for two years from 2010, and was chair of the Nominating Committee from 2015.
His most recent social media posts show that he was on a motorcycle tour of Italy with his wife before his accident near Lake Como.
Stéphane and I were not close, but in our interactions I always found him knowledgeable, witty, and charming. A thoroughly nice guy.
He was also one of the very few people in the industry I’ve trusted enough to write guest posts for DI over the years. Here he is fighting the GNSO’s corner in 2012.
Stéphane is survived by his wife and, friends tell me, two children. They have our condolences, and we wish his wife a speedy recovery.
He will be missed.

40 Comments Tagged: ICANN, obituary, stephane van gelder

Some men at ICANN meetings really are assholes

Several men have been accused of sexual harassment at ICANN meetings.
A group of women have written to ICANN with five stories of how they were groped, intimidated, objectified or otherwise harassed in violation of not only common decency but also ICANN’s year-old anti-harassment policy.
They’ve not named the alleged harassers, but hinted that they may do so in future.
If we assume the stories are all the unembellished truth — and we kinda have to nowadays — then the behavior described is unambiguously out of order.
Fortunately, none of the allegations rise to the level of the obviously seriously criminal. In these cases we appear to be talking more Hoffman than Weinstein.
But we’re not talking about bizarro Cheesesandwichgate-level interactions either. The stories allege groping, simulated sexual activity, and physical restraint, among other things.
In one allegation, a woman claims a drunk man touched her rear during a social interaction.
In another, a man is alleged to have attempted to let himself into a woman’s hotel room, prompting her to block the door from the inside with a chair, after his earlier advances were rebuffed.
Another woman claims a man she had never met chose, as his opening conversational gambit, to compliment her appearance and inquire after her marital status — during a daytime coffee break for crying out loud — and then grabbed her waist and wrists to prevent her from leaving.
“If you want to start a conversation, ask what I do, what do I work with and why am I here,” the woman is quoted as saying. “Do not acknowledge physical attributes and reduce me to this.”
“If you want to talk to women in a professional setting, do not tighten her wrists, do not grab her waist. Do not ask whether she is married or not,” she said. “Regardless, you should respect her integrity, not her marital status.”
Another man is accused of simulating a sex position with a woman during a cocktail event.
A fifth is accused of “body-blocking” a woman as she attempted to leave a room.
The letter states:

These actions which are definitely categorized as harassment and even assault, would not only affect the woman who went through the incident but it would also lead to several probable repercussions such as (1) Her withdrawal from the community and physical presence. We all know how important being present in meetings is on different levels of engagement in and outside meetings (2) When no solid response from the community is done towards the harasser, there can definitely be an increase in aggressive characters of harassers as there would be no accountability to stop them (3) With the increase in harassment there surely will be a decrease in the representation of young women’s voices in any proceeding which defies the core concept of diversity.

The letter (pdf) is unsigned, and ICANN broke with its usual practice of listing the sender on the correspondence page of its web site.
The letter also does not name any of the accused men, but it and a related comment from a group of women at the public forum at ICANN 61 last week, said the women “refrain from using names for now, in order to keep the focus on the topic and not the person”.
It’s been DI practice to not name either party concerned in such allegations, even when we know who they are.
While the anti-harassment policy exists to deal precisely with the kinds of behaviors outlined in the letter, we reported in November that the ICANN Ombudsman had received no complaints whatsoever invoking the policy, even after the post-Weinstein sea change in workplace sexual politics.
But the letter-writers say this is because the current Ombudsman, Herb Weye, is a man, and women are sometimes reluctant to report such incidents to a man. The letter states:

There should be a woman ombudsperson for harassment reporting. It has been proven by several studies that given the sensitivity of the issue, harassment reports are more prone to be tackled and come forth with, when the ombudsperson is (a) a woman (b) an expert in gender-related issues and mitigating harassment risks

They’re also not confident that the policy, which has yet to be tested, will cause more good than harm.
They also want all ICANN meeting delegates to read the harassment policy as a condition for attendance, and for signage at the meetings to warn against inappropriate behavior.
In response to the public forum comments, ICANN vice-chair Chris Disspain promised that the board will respond to the women’s letter, adding that the Ombudsman is taking a look at how the harassment policy has been implemented.
“It’s very important that ICANN is a safe place for everyone,” chair Cherine Chalaby told the women. “The more we raise awareness, the more it is safe.”
The message to certain blokes at ICANN meetings seems pretty clear: stop being assholes.
Like most places of work, the ICANN community is resplendent with examples of people forming lasting romantic relationships — or even just getting laid — but none of them began with a man grabbing a woman’s backside without her consent.

7 Comments Tagged: harassment, ICANN, icann 61, Ombudsman, sexual

Cybersquatting cases up because of .com

The World Intellectual Property Organization handled cybersquatting cases covering almost a thousand extra domain names in 2017 over the previous year, but almost all of the growth came from complaints about .com names, according to the latest WIPO stats.
There were 3,074 UDRP cases filed with WIPO in 2017, up about 1.2% from the 3,036 cases heard in 2016, WIPO said in its annual roundup last week.
That’s slower growth than 2016, which saw a 10% increase in cases over the previous year.
But the number domains complained about in UDRP was up more sharply — 6,370 domains versus 5,374 in 2016.

WIPO said that 12% of its 2017 cases covered domains registered in new gTLDs, down from 16% in 2016.
If you drill into its numbers, you see that 3,997 .com domains were complained about in 2017, up by 862 domains or 27% from the 3,135 seen in 2016.
.com accounted for 66% of UDRP’d domains in 2016 and 70% in 2017. The top four domains in WIPO’s table are all legacy gTLDs.
As usual when looking at stats for basically anything in the domain business in the last few years, the tumescent rise and meteoric fall of .xyz and .top have a lot to say about the numbers.
In 2016, they accounted for 321 and 153 of WIPO’s UDRP domains respectively, but they were down to 66 and 24 domains in 2017.
Instead, three Radix TLDs — .store, .site and .online — took the honors as the most complained-about new gTLDs, with 98, 79, and 74 domains respectively. Each of those three TLDs saw dozens more complained-about domains in 2017 than in 2016.
As usual, interpreting WIPO’s annual numbers requires caution for a number of reasons, among them: WIPO is not the only dispute resolution provider to handle UDRP cases, rises and falls in UDRP filings do not necessarily equate to rises and falls in cybersquatting, and comparisons between .com and new gTLDs do not take into account that new gTLDs also have the URS as an alternative dispute mechanism.

1 Comment Tagged: cybersquatting, ICANN, new gTLDs, trademarks, udrp, wipo

Privacy could be a million-dollar business for ICANN

ICANN has set out the fees it plans to charge to officially accredit Whois proxy and privacy services, in the face of resistance from some registrars.
VP of finance Becky Nash told registrars during a session at ICANN 61 last week that they can expect to pay $3,500 for their initial accreditation and $4,000 per year thereafter.
Those are exactly the same fees as ICANN charges under its regular registrar accreditation program.
Registrars that also offer privacy should expect to see their annual ICANN flat fees double, in other words. Per-domain transaction fees would be unaffected.
The up-front application fee would be reduced $2,000 when the privacy service is to be offered by an accredited registrar, but it would stay at $3,500 if the company offering service is merely “affiliated” with the registrar.
Nash said all the fees have been calculated on a per-accreditation basis, independent of the volume of applications ICANN receives.
Director of registrar services Jennifer Gore said that while ICANN has not baked an estimate of the number of accredited providers into its calculations, registrars have previously estimated the number at between 200 and 250 companies.
That would put the upper end of annual accreditation fees at $1 million, with $875,000 up-front for initial applications.
Volker Greimann, general counsel of the registrar Key-Systems, pointed out during the session that many registrars give away privacy services for free or at cost.
“This just adds cost to an already expensive service that does not really make money for a lot of providers,” he said.
He suggested that the prices could lead to unexpected negative consequences.
“Pricing this in this region will just lead to a lot of unaccredited providers that will switch names every couple months, an underground that we don’t really want,” he said. “We want to have as many people on board as possible and the way to do that is to keep costs low.”
“Pricing them out of the market is not the way to attract providers to join this scheme,” he said.
Nash responded that registrars are forbidden under the incoming privacy/proxy policy from accepting registrations from unaccredited services.
She added that the fees have been calculated on a “cost-recovery” basis. Costs include the initial background checks, outreach, contract admin, compliance, billing and so on.
But some registrars expressed skepticism that the proposed fees could be justified, given that ICANN does not plan to staff up to administer the program.
Another big question is whether proxy/privacy services are going to continue to have value after May this year, when the European Union’s General Data Protection Regulation kicks in.
The current ICANN plan for GDPR compliance would see individual registrants have all of their private information removed from the public Whois.
It’s not currently clear how many people and what kinds of people will continue to have access to unmasked Whois, so there are likely still plenty of cases where individuals might feel they need an extra layer of protection — if they live in a dictatorship and are engaged in rebellious political speech, for example.
There could also be cases where companies wish to mask their details ahead of, say, a product launch.
And, let’s face it, bad actors will continue to want to use privacy services on domains they intend to misuse.
The proxy/privacy policy came up through the formal GNSO Policy Development Process and was approved two years ago. It’s currently in the implementation phase.
According to a presentation from the ICANN 61 session, ICANN hopes to put the final implementation plan out for public comment by the end of the month.

3 Comments Tagged: gdpr, ICANN, icann 61, ppsai, privacy, proxy, whois

Three more dot-brands throw in the towel

Two companies have told ICANN they no longer wish to operate some of their dot-brand gTLDs.
First, Sony has decided to junk its .xperia TLD.
Xperia is a brand of mobile phones the company sells. The matching gTLD, which entered the DNS root mid-2015, only ever had the contractually mandated nic.xperia delegated.
Sony still has .sony and .playstation active. The latter doesn’t seem to have any live web sites, but .sony is seeing some light usage with sites such as pro.sony and lostinmusic.sony.
The next dot-brand to get ditched is .meo, owned by leading Portuguese mobile telco MEO.
MEO has also dumped .sapo, which is its ISP brand.
Again, neither gTLD had never seen any action beyond their nic. sites, despite being delegated over three years ago.
Both companies told ICANN in January that they wish to end the Registry Agreement contracts.
ICANN last week decided not to open any of the strings for redelegation and opened up its decision for comments.

1 Comment Tagged: .meo, .sapo, dot-brands, new gTLDs, sony, termination