The price of ICANN transparency: $2.6m

ICANN has estimated that it will need an extra $2.6 million on its fiscal 2012 budget to cover the cost of becoming more transparent and accountable.
In March, the organization decided to implement the 27 recommendations of its Accountability and Transparency Review Team, and last week the board asked its finance committee to look into budgeting the project.
The cost is estimated at $2.6 million for fiscal 2012, which begins in July, according to the resolution passed by the board on Thursday.
That’s much more than the initial estimate of $965,000 mentioned in staff briefing documents (pdf) provided to the board before its meeting in March, which excluded the ATRT recommendation that ICANN’s directors receive compensation.
The extra cash is required to hire additional staff and pay for consulting services. Presumably some of it will now also be needed to pay the board.

Niue: the myth of the “Wifi Nation”

The tiny Pacific island of Niue is commonly referred to as the world’s first and only “Wifi Nation”.
There was a lot of feel-good press coverage back in 2003, when the Massachusetts-based manager of the .nu country-code top-level domain started deploying wireless internet on the island.
NU Domain said at the time that it was “building the world’s first nation-wide wifi Internet access service, all at no cost to the public or the local government” (pdf)
This led to major media outlets, such as the BBC, reporting the line: “The free wi-fi link will be accessible to all of Niue’s 2,000 residents as well as tourists and business travellers.”
This story has remained in the media consciousness to this date, encouraged by the registry.
Just this week, NU Domain’s charitable front operation, the IUSN Foundation, was fluffily claiming that it has provided Niue with “the world’s only nation-wide free Internet”.
Even ICANN’s Kiwi chairman, Peter Dengate Thrush, spread the meme during a recent interview (audio), saying Niue had “installed free wifi across the entire island”.
There is just one problem with the “Wifi Nation” story: it’s bollocks.
This is what Niue’s Premier, Toke Talagi, had to say to Australian radio (audio) this week:

The internet services are unreliable, they’re not available throughout the island, and if you do want internet services connected up to your home you have to pay for it. Some people as I understand it have been paying up to $3,000 [$2,400] just for the installation of the wifi.
…
We’re never quite certain about what that “free” internet services is about, because we’ve had to pay.

According to Talagi, the wifi network provided by IUSN does not cover every village on the island, and users have to pay for it. The free wifi nation is neither free nor nationwide.
Even IUSN, while continuing to make its claims about nationwide wifi, admitted a year ago, seven years after the “wifi nation” claims were first made, that “villagers have been waiting to get online for some time”.
According to Talagi, the lack of reliable internet access is such a big problem that the Niuean government has had to take matters into its own hands and build its own ISP.
It is close to completing its own wired and wireless internet infrastructure, at the cost of $4.8 million, according to reports.
Niue discussed its needs with IUSN in 2009 and 2010, Talagi said, but “they felt they didn’t need to discuss these particular matters, that the services they were providing for us were adequate”.
It appears that IUSN doesn’t even pay to maintain its own equipment. This quote comes from a locally produced newsletter dated April 2009:

While IUSN is committed to provide free internet for its residents it is up to the users of this service to look after and maintain the internet enabling facilities.

That came from a report about residents of one of the island’s villages holding a fund-raiser in order to collect the $2,400 required to fix a wifi mast that had been damaged in a lightning storm (a common problem).
The per capita GDP of Niue, incidentally, is $5,800. Its citizens are not starving, but by the measure of its estimated GDP, about $10 million, it’s one of the poorest nations on the planet, reliant heavily on aid from nearby New Zealand.
According to Talagi and other sources, good internet access is not only required for economic reasons such as boosting the tourism industry.
Fast, reliable connectivity would also enable important human services, such as remote video diagnoses to be performed by overseas medical specialists, which the island lacks.
Niue’s ongoing economic problems come about largely because, other than fishing, it has very few natural resources to exploit.
A notable industry in the past has been the export of postage stamps to overseas collectors.
That business made headlines recently when a stamp was issued, celebrating the marriage of Prince William to Kate Middleton, which featured a perforation separating bride and groom.
There’s also talk of setting up a casino on the island, to boost revenues.
One asset it does have, at least on paper, is its top-level domain, .nu, which has proven popular in Sweden, where the word “nu” means “now”.
However, other than the lackluster internet connectivity provided by IUSN, Niue apparently does not see any significant revenue from the sale of .nu domain names.
According to IANA records, the .nu domain is officially delegated to the IUSN Foundation, previously known as the Internet Users Society – Niue.
The technical back-end provider is WorldNames Inc, which also operates as a registry/registrar under the brand NU Domain.
IUSN’s contact address is a PO Box in Niue, probably due to the fact that all ccTLD registry operators have to be based in the country they purport to represent.
The IUSN’s domain name, iusn.org, is registered to the same address as WorldNames and NU Domain, in the leafy Boston suburb of Medford, MA.
Most of the company’s business is done in Sweden, where most of its staff are based.
WorldNames has been in control of .nu since 1997, when its founder, Bill Semich, in partnership with a American ex-pat living on the island, managed to acquire the IANA delegation, pre-ICANN.
By several accounts, Niue has been trying to reclaim .nu from Semich for almost as many years.
In 2003, the government hired an American lawyer, Gerald McClurg, to be its representative on ICANN’s Governmental Advisory Committee and attempt to secure a redelegation.
That same year, McClurg made a submission to the International Telecommunications Union (.doc), in which he alleged that the nation was tricked out of its domain:

In 1997 IANA, without the approval of the Niuean Government, delegated the ccTLD for Niue to a businessman, William Semich, who lives in the United States. The advisor to the Government at that time was an ex-peace corp volunteer named Richard Saint Clair. Mr Saint Clair told the Government that the name meant nothing, that it was of no value or significance, and there was nothing that could be done. Shortly thereafter, Mr. Saint Clair then left his post as advisor and joined with Mr Semich in his organization – IUSN. The Government of Niue has been working every since to regain its ccTLD.

The Niuean government has actually passed a law, the Communications Amendment Act 2000, which states: “.nu is a National resource for which the prime authority is the Government of Niue”.
It also established the Niue Information Technology Committee, which “shall be the only designated Registry Manager of the Niue ccTLD .nu.”
Yet, eleven years on, IUSN is still the registry manager for .nu.
Talagi said in his radio interview this week that Niue was preparing to submit a redelegation request to ICANN/IANA in February last year, which is in line with what I was hearing at the time.
I have in my possession documentation from a European domain name registrar, dated March 2010, offering to take over the management of .nu on a not-for-profit basis.
It’s not clear to me whether Niue’s redelegation request is still active. Under current IANA practices, ICANN does not discuss pending ccTLD redelegation requests.
But I suspect IUSN has little interest in handing .nu back to Niue.
While registration data is not easy to come by, the number that has been reported frequently over the years, and as recently as 2008, is 200,000.
At 30 euros ($44) per year for the standard service from NU Domain, that’s close to a $9 million business just from domain registration fees.
That may not be much on the grand scheme of things, but it would certainly be material to a nation so reliant on hand-outs as Niue.
But IUSN is very protective of its asset.
Take a look at the Accountability Framework – one of the methods by which ICANN establishes formal relationships with ccTLD managers – that IUSN and ICANN signed in 2008 (pdf).
ICANN has signed 26 Accountability Frameworks over the last five years. They’re all very similarly worded, but the one it signed with IUSN has a notable addition not found in any of the others.
All ccTLDs’ Accountability Frameworks call for the TLD to be managed “in a manner that is consistent with the relevant laws of [insert country name]”.
But the .nu agreement is the only one to also make a specific reference to RFC 1591 and ICP-1, two rules dating from the 1990s that govern how ccTLDs are redelegated from one organization to another.
While ICP-1 gives governments a significant voice in redelegation requests, both documents state that IANA should only redelegate a TLD when both the winning and losing parties agree to the transfer.
The only notable exception to the rule is when the incumbent registry manager has been found to have “substantially misbehaved”, which I understand to be quite a high bar.
With that in mind, it’s far from obvious whether Niue stands any chance of getting its ccTLD redelegated to an approved registry any time soon.
According to a recent report (pdf) from ICANN’s ccNSO, IANA has redelegated ccTLDs in cases where the losing registry fought the decision, but its procedures for doing so are utterly opaque.

ICANN advised against director salaries

ICANN’s legal staff advised its board of directors against rushing to grant themselves a pay packet, according to documents released today.
At its San Francisco meeting last month, ICANN’s board voted to adopt a package of 27 measures designed to improve the organization’s accountability and transparency.
One of the recommendations, provided by the Accountability and Transparency Review Team in December, asked the board to quickly implement a “compensation scheme” for ICANN’s voting directors.
Other than salaried president Rod Beckstrom, currently only the chairman, Peter Dengate Thrush, is paid for his work on the board.
But briefing documents provided to the board prior to the San Francisco vote, published today (pdf and pdf), reveal that ICANN staff recommended adopting only 26 of the 27 ATRT recommendation.
The original ATRT recommendation #5 reads:

The Board should expeditiously implement the compensation scheme for voting Directors as recommended by the Boston Consulting Group adjusted as necessary to address international payment issues, if any.

And the ICANN staff recommendation to the board reads:

Staff recommends that the Board not implement ATRT Recommendation #5 – a compensation scheme for voting Board Directors – at this time, but give adoption and implementation further consideration as detailed in the staff’s proposed implementation plan

Regardless, the board voted to adopt all 27 ATRT recommendations in San Francisco, including the board compensation plan idea. This was broadly welcomed by the community.
The precise reasoning behind the staff’s recommendation is not clear – the rationale has been redacted from the briefing documents – but director Bruce Tonkin gave a hint during remarks at the open board meeting in San Francisco, saying:

There are legal requirements for how a board could pass a motion to decide to compensate board members, which is one of the recommendations, and then there are obviously budget implications of doing that.
So just the legal steps that need to be followed will take a bit of time. Not years, but will take some months.

The ATRT report was fairly comprehensive, covering everything from how ICANN selects its board to how it interacts with its Governmental Advisory Committee, to what information it publishes on its web site.
The report also gave ICANN deadlines to hit on many recommendations, many of them June 2011.
But it appears from the just-published briefing documents that ICANN intends to miss those deadlines in several cases, due to the complexity of the work involved, by a few months to as much as a year or more.
In other, simpler, cases, ICANN has already met the recommendations. Many of ICANN’s policy-making processes are still due to get a shake-up, but some changes will take longer than expected.

Registrar threatened over “stolen” Facebook domain

ICANN has threatened to terminate the domain name registrar EuroDNS for failing to transfer a typo domain lost in a UDRP case to Facebook.
But EuroDNS says it is subject to a court case in its home country, Luxembourg, which has prevented it handing over the name.
The original registrant of facebok.com lost a slam-dunk UDRP case back in September 2010. He didn’t even bother defending the case.
But over half a year later, he’s still in control of the domain, and he’s using it to recruit folk into a shady-looking (but probably legal) subscription text messaging service.
EuroDNS is the registrar of record for the domain, and like all registrars is responsible for transferring domains lost under the UDRP to the winning party, in this case Facebook.
ICANN’s compliance department – my guess is under pressure from Facebook – has therefore threatened EuroDNS with termination unless it hands over the domain in the next three weeks.
This is noteworthy because EuroDNS isn’t the kind of tiny, fringe outfit ICANN usually files compliance notices against. It’s a generally respectable business. It even shows up to ICANN meetings.
EuroDNS deputy general counsel Luc Seufer tells me that the company was fully prepared to transfer the domain – it had even sent the authorization codes to Facebook – but it found itself on the receiving end of a lawsuit claiming that the domain had been “stolen”.
Somebody in Luxembourg, it seems, has sued to reclaim an obvious typo domain that’s probably going to be transferred to Facebook anyway.
“We are therefore in an incredible position where if we transfer the name before the judge’s ruling we will be accountable in our own country and if we don’t transfer the name we are in breach of the [Registrar Accreditation Agreement],” said Seufer.
The Luxembourg case has not yet made it to court, hence EuroDNS’s delay, he said. ICANN is aware of the action, and has seen the court papers, he said.
According to ICANN’s breach notice (pdf), the only way for EuroDNS to avoid its obligation under the UDRP is to show proof that the original registrant has sued Facebook to keep the domain.
But the case in question was filed by a third party claiming to be the rightful owner of the domain, not the original registrant. EuroDNS seems to be trapped between a rock and a hard place.
Seufer said the company is prepared to hand over the domain, adding:

Should we simply ignore a judiciary court case against us in our own country – that could prevent us from operating the transfer since it is was asked of the judge – because of our RAA’s obligations?

The domain in question, facebok.com, currently redirects to a series of sites asking visitors to fill in a survey to win a Mac.
Those who are duped by it are actually signing up to a text service that costs, in the UK, £4.50 ($7.40) per week.

Registry avoids .jobs shut-down

Employ Media has come to a deal with ICANN to avoid having its .jobs registry contract revoked, at least for the next few weeks.
Following discussions with ICANN’s lawyers, the company plans to amend its Charter, and has agreed to stop allocating non-company-name .jobs domain names until May 6.
ICANN threatened to terminate the .jobs registry deal in February, after Employ Media started allocating thousands of premium vocational and geographic domains to a partner, the DirectEmployers Association, to act as entry points for Universe.jobs.
In a breach notice (pdf), ICANN said that this use of .jobs domains “is inconsistent with the purpose stated in the .JOBS Charter and represented to the ICANN community”.
The .JOBS Charter ostensibly restricts registrations to human resources professionals, but in practice there’s a great big loophole that allows anybody to cheaply qualify for a domain.
In February, ICANN general counsel John Jeffrey told Employ Media:

By not establishing any meaningful restrictions on who may register second level registrations in the .JOBS TLD, Employ Media put in operation a TLD where anyone can register names, thus defeating the purpose for which the sponsored TLD came into existence.

In its response, the registry noted that it had followed ICANN’s proper procedures for introducing new “registry services”, such as the Phase Allocation Plan that allowed it to seed Universe.jobs.
It accused ICANN of bending to the wishes of the .JOBS Charter Compliance Coalition, a group of independent jobs sites operators that had objected to Universe.jobs.
Employ Media’s chief executive Brian Johnson wrote:

This is a sad day for both the Internet community and the international human resource management community. ICANN should be promoting competition and working cooperatively with its contractual parties, but instead is choosing to ignore the plain meaning of its contract with Employ Media in order to appease some apparently well‐financed and well‐connected provocateurs.

Since that letter (pdf) was sent, ICANN and the registry have been engaged in private discussions aimed at resolving the conflict, as allowed by the registry agreement.
In the latest set of correspondence, exchanged over the last week, it has emerged that ICANN has agreed to give Employ Media time to remedy the situation by amending its Charter.
The letters do not reveal whether the amendments will allow Employ Media to continue to offer Universe.jobs or not. I suspect they will.
The amendments may require the company to consult with its nominal sponsor, the Society for Human Resource Management.
ICANN wants a proposed Charter amendment on its desk by May 2. It has agreed to take no further action related to the breach of contract allegations until May 6.

New TLDs timetable tightened

ICANN’s effort to squeeze out a process for approving new top-level domains has been about as easy and painless as giving birth, so it perhaps appropriate that it now expects to take at least nine months to gestate the very easiest applications.
The new version of the Applicant Guidebook, published Saturday, makes a number of changes to the expected new TLDs timetable, including the addition of an extra month to the minimum likely processing time for non-controversial strings.
This is not, as you might think, a result of the new objection powers granted to the Governmental Advisory Committee.
(UPDATE: On closer analysis, it appears that the timetable has in fact been rejiggered in order to give more time to the GAC’s Early Warning mechanism. Thanks to Mike, in the comments, for the correction.)
The Administrative Check part – the bit where ICANN goes through the applications to make sure they’ve all been correctly filed – that has been extended, from four weeks to eight.
ICANN has also shortened the first-round application-filing window by a month, to 60 days, off-setting the extended processing time.
New TLDs may start entering the root around the same time they were previously expected.
The timetable for the launch of new TLDs now looks a little like this:
June 20 – Applicant Guidebook approved in Singapore.
July-October 2011 – four-month communication/outreach period.
November-December 2011 – first-round application window
October 2012 – first new TLDs delegated to DNS root.
The new Guidebook advises applicants to avoid waiting to the last minute to file their applications, due to the complexity of the new TLD Application System (TAS) it’s created.
Given the application period is likely to end shortly after the end of year holiday period, I expect applicants will have plenty of impetus to get their applications in early without encouragement.

ICANN brings “loser pays” to domain disputes

ICANN has significantly strengthened brand-owner protections in new top-level domains by proposing, amongst other things, a new “loser pays” model for some cybersquatting disputes.
The Uniform Rapid Suspension process, which is designed to give trademark owners a quick, cheap way to take down obvious examples of cybersquatting, may now occasionally carry a response fee.
According to ICANN’s newly revised Applicant Guidebook, which was published early this morning:

A limited “loser pays” model has been adopted for the URS. Complaints listing twenty-six (26) or more disputed domain names will be subject to an Response Fee which will be refundable to the prevailing party. Under no circumstances shall the Response Fee exceed the fee charged to the Complainant.

In other words, if a somebody registers more than 25 domains that appear to infringe upon the trademarks of a single company, they will have to pay a few hundred dollars, refundable, if they want to defend their case. Judging from UDRP history, this will likely apply to very few people.
The number 25 comes from the May 2009 report of ICANN’s Implementation Recommendation Team, which devised many of the new gTLD program’s rights protection mechanisms.
This change is one of several made in the new Guidebook, addressing concerns raised by the Governmental Advisory Committee, which had consulted closely with the IP lobby.
The GAC didn’t get everything it wanted, however. It had asked for repeat cybersquatters to lose their right to respond under the URS, but ICANN declined, citing the need for due process.
But the Guidebook does now also require new TLD registry operators to offer two types of rights protection mechanism during their launch phase, as the GAC had requested.
Whereas earlier drafts mandated either a Trademark Claims service or a Sunrise period, now registries will have no choice: they have to offer both at a minimum.
The Trademark Claims services notifies registrants if they try to register a domain name that matches a trademark registered in a central Trademark Clearinghouse.
The registrant will have to certify that they’re not infringing any rights before they get the domain. If they do register it, the affected trademark holder will receive a notification that the domain has been registered and can choose to take action such as filing a URS claim.
The idea behind the service is to deter cybersquatters, possibly reducing brand owners’ costs from having to defensively register their names in all new TLDs.
The Sunrise period, which is now also mandatory, is not entirely dissimilar to the sunrise periods we’ve come to expect from new TLD launches over recent years.
The new Guidebook states that the Trademark Claims service must be offered for at least 60 days after a new TLD enters general availability and the Sunrise must be at least 30 days before.
The fact that both services are now mandatory has helped ICANN address the thorny question of what should constitute a valid trademark.
Earlier drafts of the Guidebook required trademarks to have been subject to “substantive review” – a check by a national authority that the trademark is for real and in use.
The worry was that speculators could game the system by picking up large numbers of trademarks in countries that give them away like candy. It’s happened before.
But the review requirement was criticized by the GAC and others as it excluded trademarks in much of the world outside of the US.
In response to these criticisms, ICANN has removed the reference to substantive review. Instead, the yet-to-be-decided manager of the Trademark Clearinghouse will be given the task of validating that each trademark submitted is legit.
Companies need only submit a declaration and a single piece of evidence of use in order to get into the Clearinghouse, thus enabling them to partake of the Sunrise.
No such validation will be required in order to participate in the Trademark Claims service, though brand owners will need to be listed in the Clearinghouse for both mechanisms.
Evidence of use will also be needed to file URS complaints, but that can be done separately at the time of filing, with no need for a Clearinghouse registration.
ICANN chairman Peter Dengate Thrush, himself an IP lawyer, once stated, possibly in jest, that no matter what you do, you can be certain that IP lawyers will demand more protections.
Whether the rights protections mechanisms included in the Guidebook are now sufficient to calm trademark interests’ nerves remains to be seen.

ICANN gives governments powers over new TLDs

ICANN has made some significant concessions to government demands in the newly published revision of its new top-level domains Applicant Guidebook.
After lengthy consultations with its Governmental Advisory Committee over the last few months, ICANN has updated the rulebook to address the vast majority of GAC concerns.
We’ve gone from the “proposed final Applicant Guidebook” published in November to the “April 2011 Discussion Draft” that appeared on the ICANN web site in the wee hours of this morning.
On first perusal, it appears that ICANN has walked the fine lines between GAC advice, hard-fought community consensus and common sense more or less successfully.
While the new Guidebook gives plenty of ground to the GAC, making it a more integral part of the new TLDs approval process, it avoids adopting some of its more problematic requests.
In this post, I’ll look at the powers ICANN has given to governments to object to TLDs.
Early Warning System
While ICANN has sensibly not given individual governments the right to veto TLDs they are not happy with, they do get substantially more input into the approval process than in previous drafts.
The major update to the Guidebook is a new Early Warning system that will allow governments to pre-object to TLDs they don’t like.
An Early Warning, which can only be filed by the GAC chair, is “an indication that the application is seen as potentially problematic by one or more governments.”
Applicants in receipt of such a warning will have 21 days to decide whether to drop out of the process, receiving a $148,000 refund, 80% of their $185,000 application fee.
But they won’t have to. The warning is just a heads-up that the GAC or some of its members may formally object at a later stage. A warning does not represent a GAC consensus position.
The Early Warning process will run for 60 days, at the same time as the public comment period that begins the day the applications are published.
Advice of Doom
Any applicants that decide to ignore such a warning face the possibility of receiving a formal GAC objection, which could come at any point in the first seven months after the applications are published.
This is now being called “GAC Advice on New gTLDs”. It could be quite a powerful tool:

GAC Advice on New gTLDs that includes a consensus statement from the GAC that an application should not proceed as submitted, and that includes a thorough explanation of the public policy basis for such advice, will create a strong presumption for the Board that the application should not be approved.

This is pretty close to a GAC veto, but it crucially requires GAC consensus. The Guidebook explains:

GAC Advice on New gTLDs should identify objecting countries, the public policy basis for the objection, and the process by which consensus was reached.

Even if the GAC reaches consensus, the ICANN board will be able to overrule its objections in accordance with its bylaws, in much the same way it just did with .xxx (in practice, I suspect .xxx may ultimately prove a fairly unique exception to the rule).
The Guidebook indicates that any wishy-washy, non-consensus, politician-speak advice given by the GAC will not be considered grounds for rejecting an application. The objection must be specific, grounded, and it must have support.
Importantly, ICANN has not conceded to the GAC’s request to allow applicants to amend their applications to remedy the GAC’s concerns.
As I noted earlier in the week, this could have led to companies gaming the system, and ICANN has ruled out amendments for precisely that reason.
Freebies
Individual governments will of course be allowed to object to any application using any of the other procedures that the Guidebook allows, such as the Community Objection.
ICANN’s problem is that these processes carry third-party fees, and governments don’t think they should have to pay these fees (for some reason that’s never been adequately explained).
Addressing this concern, the new Guidebook says that ICANN will cover each national government to the tune of $50,000 to fund a single objection.
That’s a total of potentially well over $1 million, funded from ICANN’s reserves. ICANN expects that governments will coordinate their objections to limit its costs.
Overall, it appears that ICANN has addressed pretty much everything the GAC wanted in terms of objections procedures. With a couple of reasonable exceptions, the GAC has received what it asked for.
Members may not be completely happy with ICANN’s decrees on what form GAC advice must take in order to have a useful impact, but in general it seems that this could well now be a closed issue.
In my next post, I’ll look at how intellectual property protection changes in the new Guidebook.

.xxx domains go live

Click here: icmregistry.xxx, then come back.
That’s right. After ICM Registry’s almost 11 years of campaigning, and almost $20 million in legal and other expenses, .xxx domain names are actually live in the domain name system.
ICANN, IANA, the US government and VeriSign, in that order, have all agreed to delegate the internet’s newest gTLD, and the first few .xxx domains went live within the last couple hours.
The domains sex.xxx and porn.xxx are now also resolving to placeholder sites. They’re currently “safe for work”, but possibly not for much longer.
IANA has a .xxx page, complete with a lengthy delegation report (in a snazzy new pdf format) that broadly explains the convoluted process ICANN used to ultimately, albeit reluctantly, approve the TLD.

North Korean domain to change hands

ICANN is set to redelegate .kp, the country-code top-level domain for North Korea, when its board of directors meets next week.
It’s less than four years since .kp was first created. In September 2007, IANA delegated the ccTLD for the first time to the Korea Computer Center, a Pyongyang-backed governmental organization.
The technical side of the registry is currently handled by KCC Europe, a German company, but while some .kp domains still resolve, the official registry web site has been offline for months.
The redelegation is part of the ICANN board’s consent agenda. This means that, barring surprises, it will simply be rubber-stamped with no substantive discussion.
Because ccTLD redelegations are handled in private, we won’t know who the new registry manager is until after the handover happens and the IANA report is published.
In other ccTLD news, ICANN may also create three new internationalized domain name ccTLDs, for Serbia (.срб ), Algeria (الجزائر) and Morroco (المغرب).
Those delegations are part of the board’s regular agenda for its April 21 meeting, and will be discussed.