Amazon and Google to fight over .kids at auction

Amazon, Google and a third applicant are scheduled to fight for control of the new gTLDs .kid or .kids at auction.
It’s the first ICANN gTLD auction to be scheduled since a Verisign puppet paid $135 million for .web in July 2016.
According to ICANN documentation, .kid and .kids will go to auction January 25, 2018.
The winning bid will be added to ICANN’s quarter-billion-dollar stash of auction proceeds, rather than shared out between the applicants.
Even though two different strings are at stake, it will be a so-called “direct contention” auction, meaning only .kids or .kid will ultimately go live.
Google, the sole applicant for .kid, had filed String Confusion Objections against .kids applications from Amazon and DotKids Foundation and won both, meaning the three applications were lumped into the same contention set.
Unless DotKids has a secret sugar daddy, it seems probable that the internet will next year either get a .kid gTLD operated by Google or a .kids gTLD operated by Amazon.
DotKids had applied as a “community” application and attempted to shut out both rivals and avoid an auction by requesting a Community Priority Evaluation.
However, it comprehensively lost the CPE.
Child-friendly domain spaces have a poor track record, partly due to the extra restrictions registrants must agree to, and are unlikely to be high-volume gTLDS no matter who wins.
Neustar operated .kids.us for 10 years, following US legislation, but turned it off in 2012 after fewer than 100 web sites used the domain. It made the decision not to reintroduce it in 2015.
The Russian-language equivalent, .дети, has been live for over three years but has only around 1,000 domains in its zone file.
The .kids/.kid auction may not go ahead if the three applicants privately negotiate a deal soon, but they’ve had over a year to do so already and have apparently failed to come to an agreement.

ICANN chief tells industry to lawyer up as privacy law looms

The domain name industry should not rely on ICANN to protect it from incoming EU privacy law.
That’s the strong message that came out of ICANN 60 in Abu Dhabi last week, with the organization’s CEO repeatedly advising companies to seek their own legal advice on compliance with the General Data Protection Regulation.
The organization also said that it will “defer taking action” against any registrar or registry that does not live up its contractual Whois commitments, within certain limits.
“GDPR is a law. I didn’t come up with it, it didn’t come from ICANN policy, it’s the law,” Marby said during ICANN 60 in Abu Dhabi last week.
“This is the first time we’ve seen any legislation that has a direct impact on our ability to make policies,” he said.
GDPR is the EU law governing how companies treat the private information of individuals. While in force now, from May next year companies in any industry found in breach of GDPR could face millions of euros in fines.
For the domain industry, it is expected to force potentially big changes on the current Whois system. The days of all Whois contact information published freely for all to see may well be numbered.
But nobody — not even ICANN — yet knows precisely how registries and registrars are going to be able to comply with the law whilst still publishing Whois data as required by their ICANN contracts.
The latest official line from ICANN is:

At this point, we know that the GDPR will have an impact on open, publicly available WHOIS. We have no indication that abandoning existing WHOIS requirements is necessary to comply with the GDPR, but we don’t know the extent to which personal domain registration data of residents of the European Union should continue to be publicly available.

Marby told ICANNers last week that it might not be definitively known how the law applies until some EU case law has been established in the highest European courts, which could take years.
A GNSO working group and ICANN org have both commissioned legal studies by European law experts. The ICANN one, by Swedish law firm Hamilton, is rather more comprehensive and can be read here (pdf).
Even after this report, Marby said ICANN is still in “discovery” mode.
Marby encouraged the industry to not only submit their questions to ICANN, to be referred on to Hamilton for follow-up studies, but also to share whatever legal advice they have been given and are able to share.
He and others pointed out that Whois is not the only point of friction with GDPR — it’s a privacy law, not a Whois law — so registries and registrars should be studying all of their personal data collection processes for potential conflicts.
Because there is very likely going to be a clash between GDPR compliance and ICANN contract compliance, ICANN has suspended all enforcement actions against Whois violations, within certain parameters.
It said last week that: “ICANN Contractual Compliance will defer taking action against any registry or registrar for noncompliance with contractual obligations related to the handling of registration data.”
This is not ICANN saying that registries and registrars can abandon Whois altogether, the statement stresses, but they might be able to adjust their data-handling models.
Domain firms will have to show “a reasonable accommodation of existing contractual obligations and the GDPR” and will have to submit their models to ICANN for review by Hamilton.
ICANN also stressed that registries may have to undergo a Registry Services Evaluation Process review before they can deploy their new model.
The organization has already told two Dutch new gTLD registries that they must submit to an RSEP, after .amsterdam and .frl abruptly stopped publishing Whois data for private registrants recently.
General counsel John Jeffrey wrote to the registries’ lawyer (pdf) to state that an RSEP is required regardless of whether the “new registry service” was introduced to comply with local law.
“One of the underlying purposes of this policy is to ensure that a new registry service does not create and security, stability or competition concerns,” he wrote.
Jeffrey said that while Whois privacy was offered at the registry level, registrars were still publishing full contact details for the same registrants.
ICANN said last week that it will publish more detailed guidance advising registries and registrars how to avoid breach notices will be published “shortly”.

Up to 20 million people could get broken internet in domain security rollover

Twenty million people losing access to parts of the internet is considered an acceptable level of collateral damage for ICANN’s forthcoming DNS root security update.
That’s one of a number of facts and figures to emerge from recent updates from the organization, explaining its decision to delay the so-called “KSK rollover” from October 11 to some time in the first quarter next year.
The rollover will see a new Key Signing Key, used as the trust anchor for all DNSSEC-signed domains, replace the seven-year-old original.
DNSSEC protects internet users and registrants from domain-based man-in-the-middle attacks. It’s considered good practice to roll keys at each level of the DNS hierarchy periodically, to reduce the risk of successful brute-force attacks.
The root KSK update will affect hundreds of millions of people who currently use DNSSEC-compatible resolvers, such as Google DNS.
ICANN delayed the rollover after it, rather fortuitously, spotted that not all of these resolvers are configured to correctly handle the change.
The number of known incompatible servers is quite small — only about 500 of the 11,982 DNSSEC-using recursive servers initially surveyed (pdf). That represents only a very small minority of the world’s internet users, as most are not currently using DNSSEC.
Subsequent ICANN research, presented by principal researcher Roy Arends at ICANN 60 last week, showed that:

• There are currently about 4.2 million DNS resolvers in the world.
• Of those, 27,084 are configured to tell the root servers which KSKs they support (currently either the KSK-2011 or KSK-2017).
• Of those, 1,631 or 6.02% do not support KSK-2017

It was only possible to survey servers that have turned on a recent update to DNS software such as BIND and Unbound, so the true number of misconfigured servers could be much higher.
Matt Larson, ICANN’s VP of research, told DI that ICANN has identified 176 organizations in 41 countries that are currently not prepared to handle the new KSK. These organizations are fairly evenly spread geographically, he said.
Since making the decision to delay the rollover, ICANN has hired a contractor to reach out to these network operators to alert them to potential problems.
ICANN’s CEO Goran Marby has also been writing to telecommunications regulators in all countries to ask for assistance.
After the rollover, people using an incompatible resolver would be unable to access DNSSEC-signed domains. Again, that’s still quite a small minority of domains — there are only about 750,000 in .com by some accounts and apparently none of the top 25 site support it.
ICANN could roll back the change if it detects that a sufficiently large number of people are negatively affected, but that number turns out to be around 20 million.
According to its published rollover plan:

Rollback of any step in the key roll process should be initiated if the measurement program indicated that a minimum of 0.5% of the estimated Internet end-user population has been negatively impacted by the change 72 hours after each change has been deployed into the root zone.

According to InternetWorldStats, there were around 3,885,567,619 internet users in the world this June. It’s very likely more people now.
So a 0.5% threshold works out to about 19 million to 20 million people worldwide.
Larson agreed that in absolute terms, it’s a big number.
“The overall message to take away from that number, I suggest, is that a problem would have to be pretty serious for us to consider rolling back,” Larson, who was not on the team that came up with the threshold, said.
“I think that’s a reasonable position considering that, in the immediate aftermath of the rollover, there are two near-immediate fixes available to any operator experiencing problems: update their systems’ trust anchors with the new key or (less desirable from my perspective but still effective) simply disable DNSSEC validation,” he said.
He added that the 0.5% level is not a hard and fast rule, and that ICANN could be flexible in the moment.
“For example, if when we roll the key, we find out there’s some critical system with a literal life or death impact that is negatively affected by the KSK roll, I think I can pretty confidently state that we wouldn’t require the 0.5% of Internet user threshold to be met before rolling back if it looked like there would be a significant health and safety risk not easily mitigated,” he said.
The chances of such an impact are very slim, but not impossible, he suggested.
It’s not ICANN’s intention to put anyone’s internet access at risk, of course, which is why there’s a delay.
ICANN’s plan calls for any rollover to happen on the eleventh day of a given calendar quarter, so the soonest it could happen would be January 11.
Given the complexity of the outreach task in hand, the relative lack of data, and the holiday periods approaching in many countries, and ICANN’s generally cautious nature, I’d hazard a guess we might be looking at April 11 at the earliest instead.

Corwin joins Verisign

Phil Corwin, the face of the Internet Commerce Association for over a decade, today quit to join Verisign’s legal team.
He’s now “policy counsel” at the .com giant, he said in a statement emailed to industry bloggers.
He’s also closed down the consulting company Virtualaw, resigned from ICANN’s Business Constituency and from his BC seat on the GNSO Council.
But he said he would continue as co-chair of two ICANN working groups — one looking at rights protection for intergovernmental organizations (which is kinda winding down anyway) and the other on general rights protection measures.
“I have no further statement at this time and shall not respond to questions,” Corwin concluded his email.
He’s been with ICA, which represents the interests of big domain investors, for 11 years.
As well as being an ICANN working group volunteer, he’s produced innumerable public comments and op-eds fighting for the interests of ICA members.
One of his major focuses over the years has been UDRP, which ICA believes should be more balanced towards registrant rights.
He’s also fought a losing battle against ICANN “imposing” the Uniform Rapid Suspension process on pre-2012 gTLDs, due to the fear that it one day may be forced upon Verisign’s .com and .net, where most domain investment is tied up.

ICANN terminates 450 drop-catch registrars

Almost 450 registrars have lost their ICANN accreditations in recent days, fulfilling predictions of a downturn in the domain name drop-catch market.
By my reckoning, 448 registrars have been terminated in the last week, all of them apparently shells operated by Pheenix, one of the big three drop-catching firms.
Basically, Pheenix has dumped about 90% of its portfolio of accreditations, about 300 of which are less than a year old.
It also means ICANN has lost about 15% of its fee-paying registrars.
Pheenix has saved itself at least $1.2 million in ICANN’s fixed accreditation fees, not including the variable and transaction-based fees.
It has about 50 registrars left in its stable.
The terminated registrars are all either numbered LLCs — “Everest [1-100] LLC” for example — or named after random historical or fictional characters or magic swords.
The move is not unexpected. ICANN predicted it would lose 750 registrars when it compiled its fiscal 2018 budget.
VP Cyrus Namazi said back in July that the drop-catching market is not big enough to support the many hundreds of shell registrars that Pheenix, along with rivals SnapNames/Namejet and DropCatch.com, have created over the last few years.
The downturn, Namazi said back then, is material to ICANN’s budget. I estimated at the time that roughly two thirds of ICANN’s accredited registrar base belonged to the three main drop-catch firms.
Another theory doing the rounds, after Domain Name Wire spotted a Verisign patent filing covering a system for detecting and mitigating “registrar collusion” in the space, is that Verisign is due to shake up the .com drop-catch market with some kind of centralized service.
ICANN reckoned it would start losing registrars in October at a rate of about 250 per quarter, which seems to be playing out as predicted, so the purge has likely only just begun.

ICANN heading back to Morocco in 2019

ICANN has picked Morocco for its mid-year meeting in 2019.
The June 24-27 meeting, ICANN 65, will be hosted by the Mediterranean Federation of Internet Associations at the Palmeraie Resort in Marrakech. That’s the same venue as ICANN 55 in March 2016.
It’s a Policy Forum meeting, meaning it has an abridged agenda, an expected lower attendance, and a tighter focus on policy work than the other two annual meetings.
It will be sandwiched between the March meeting in Kobe, Japan and the November meeting in Montreal, Canada.
More pressingly, it now seems all but certain that ICANN is heading to Puerto Rico in March 2018 for ICANN 61, despite the extensive damage caused by Hurricane Maria in September.
During the public forum at ICANN 60 in Abu Dhabi last week, the customary spot where the next meeting’s hosts get five minutes to plug their city or nation was notably different.
Shots of landscapes, sunsets and cultural attractions were instead replaced by a series of government and local tourism officials encouraging ICANNers to visit. The message was basically: everything’s okay, it’s safe for you to come.

The convention center venue for ICANN 61 was so lightly damaged by Maria that it was actually used as the headquarters of the recovery effort immediately after the storm. You may have seen news footage of it when President Trump showed up.
ICANN said October 7 that it was monitoring the situation but that it still intended to have the March meeting in San Juan as planned.
The city would no doubt welcome the modest economic boost that a few thousand tech professionals and lawyers showing up for a week will provide.
I’m planning on attending.

Refund “options” for in-limbo gTLD applicants?

ICANN may just be a matter of weeks away from giving applicants for the .mail, .corp and .home gTLDs an exit strategy from their four years in limbo.
Its board of directors on Thursday passed a resolution calling for staff to “provide options for the Board to consider to address the New gTLD Program applications for .CORP, .HOME, and .MAIL by the first available meeting of the Board following the ICANN60 meeting in Abu Dhabi”.
It’s possible this means the board could consider the matter before the end of the year.
Twenty remaining applications for the three strings have been on hold since they were identified as particularly risky in August 2013.
A study showed that all three — .home and .corp in particular — already experience vast amounts of erroneous DNS traffic on a daily basis.
This is due to so-called “name collisions”, which come about when a newly delegated TLD is actually already in use on corporate or public networks.
Many companies use .corp and .mail already behind their firewalls, a practice sometimes historically encouraged by commercial technical documentation, and .home is known to be used by some ISPs in residential and business routers.
Both of these scenarios and others can lead to DNS queries spilling out onto the public internet, which could cause breakage or data leakage.
The solution for all new gTLDs delegated to date has been to wildcard the entire zone with the message “Your DNS needs immediate attention” for a period before registrations are accepted.
This has led to some new gTLDs with far less collision traffic seeing small but notable pockets of outrage when delegated — Google’s .prod (used by some as an internal shorthand for “production”) in 2014.
Studies to date have concentrated on the volume of error traffic to applied-for gTLDs, but last Thursday the ICANN board kicked off a study that will look at what the real-world impact of name collisions in .mail, .corp and .home could be.
It’s tasked the Security and Stability Advisory Committee with carrying out the study in conjunction with related groups such as the IETF.
But this is likely to take quite a long time, so the board also resolved to think up “options” for the 20 affected applications.
Could the applicants be offered a full refund, as opposed to the partial one they currently qualify for? Could there be some kind of deferment option, such as that offered to unsuccessful 2000-round applicants? Either seems possible.

ICANN beefs up background checks on directors amid concerns about vice-chair

ICANN is to beef up background screening procedures for its own board of directors after concerns were raised about financial integrity.
Directors in four seats that were not previously subject to screening have voluntarily agreed to checks “immediately” and ICANN has urged two of its supporting organizations to bring in such checks as standard.
Chris Disspain and Mike Silber, selected by the Country Code Names Supporting Organization, and Generic Names Supporting Organization selectees Becky Burr and Matthew Shears are these volunteers.
Neither the GNSO nor ccNSO currently screen their director picks to the same standard as other supporting organizations and the Nominating Committee.
ICANN said that they will be checked for “negative indicators such as discrepancies on a resume (including licenses, educational history and employment history), or publicly reported issues of financial mismanagement, fraud, harassment and mishandling of confidential information”.
The board passed a resolution last Thursday calling for the two SOs to bring in “the same or similar” screening procedures for future directors.
The resolution was passed minutes before the formal handover of power from outgoing chair Steve Crocker to new chair Cherine Chalaby. Disspain is the new vice-chair, replacing Chalaby.
ICANN had been put under pressure to widen its director due diligence earlier in the week by consultant and long-time ICANN community member Ron Andruff, who is known to have concerns about Disspain’s financial integrity.
Andruff spoke at an open-mic session with the board last Monday to recommend that the four anomalous directors face screening before the board was re-seated just a few days later.
“We’re talking about risk,” he said. “We’re talking about making sure that we do not put our institution that we’ve worked so hard to put into ICANN 2.0 in a place where we have four people that might have something, or not. And quite frankly, I don’t expect we’re going to find anything. I just want to make sure that we’ve checked that box,” Andruff said.
“We have the resources to do four background screenings between now and Thursday. No one expects any issues to surface. But this simple act will ensure that the institution is properly protected,” Andruff said.
Then-chair Crocker responded that it would not be possible to do the checks so quickly, but agreed in principle with the need for screening and said the board had had “substantial discussions” on the matter.
Andruff is former chair-elect of the Nominating Committee, which chooses eight directors and subjects all of its appointees to background screening.
He recently made a Freedom of Information Act request in Australia related to the circumstances leading to Disspain getting fired as CEO of local ccTLD administrator auDA in March 2016.
Disspain was let go after his relationship with the auDA board became “increasingly strained over issues of process, transparency and accountability”, according to an external review published by auDA in October last year.
auDA’s practices had “not kept pace with auDA’s growth in scale and importance to the Australian community, nor with evolving good practice in governance and accountability”, this review found.
The review did not directly allege any wrongdoing by Disspain.
A separate and currently unpublished review around the same time by PPB Advisory found that auDA had been “under-reporting” so-called “fringe benefit tax” to the Aussie tax authorities, according to auDA board meeting minutes.
FBT is tax companies must pay on employee benefits such as a company car or payment of private expenses.
There’s no clear indication in the public record that this under-reporting was directly related to benefits Disspain received, though the under-reporting very likely happened at least partially during his 15 years as CEO.
A slide deck discussing the PPB review published by auDA identified “a lack of formal policies and procedures governing how travel and expenses were managed”.
It added: “There were high levels of expenditure on international travel and reimbursement arrangements with international bodies that lacked transparency, which should have warranted a more robust process”.
All expenses incurred by ICANN’s directors and reimbursed in relation to their duties are a matter of public record.
Disspain receives not only a $45,000 annual salary but also tens of thousands of dollars in reimbursements each year, much of which is related to directors’ extensive travel obligations, these records show.
In its last reported tax year, to June 30, 2016, he received $68,437 in reimbursements, according to a published document (pdf). ICANN directly paid another $32,951 on his behalf.
A number of allegations have been made to DI (and, I believe, to other bloggers) over the last few months about alleged wrongdoing by Disspain in connection to these nuggets of information, but they’ve come from sources who refuse to identify themselves or provide corroborating evidence.
Despite efforts, I’ve been unable to independently verify these anonymous claims, which come amid turbulent times for auDA and its members, so I’ve chosen not to repeat them.
Andruff, meanwhile, has used FOI law to ask the Australian government, which has oversight of auDA, for the full PPB report, as well as documents related to the FBT issue, Disspain’s termination and his travel expenses.
Andruff and Disspain are known to have a history of friction.
Two years ago, Andruff expressed his anger after having been passed over for the job of chair of the NomCom, a role that be believes should have gone to him as chair-elect.
He lost the opportunity after the ICANN board, exercising its bylaws-permitted discretion, accepted the recommendation of its Board Governance Committee — at the time chaired by Disspain — that it be given to Stephane Van Gelder instead.
The original deadline for the Australian government response to Andruff’s FOI request was October 16, but this has been extended twice, now to November 19, due to the complexity of the request.
The eventual response will no doubt be read with interest.

Concern as ICANN shuts down “independent” security review

Just a year after gaining its independence from the US government, ICANN has come under scrutiny over concerns that its board of directors may have overstepped its powers.
The board has come in for criticism from almost everyone expressing an opinion at the ICANN 60 meeting in Abu Dhabi this week, after it temporarily suspended a supposedly independent security review.
The Security, Stability and Resiliency of the DNS Review, known as SSR-2, is one of the mandatory reviews that got transferred into ICANN’s bylaws after the Affirmation of Commitments with the US wound up last year.
The review is supposed to look at ICANN’s “execution of its commitment to enhance the operational stability, reliability, resiliency, security, and global interoperability of the systems and processes, both internal and external, that directly affect and/or are affected by the Internet’s system of unique identifiers that ICANN coordinates”.
The 14 to 16 volunteer members have been working for about eight months, but at the weekend the ICANN board pulled the plug, saying in a letter to the review team that it had decided “to suspend the review team’s work” and said its work “should be paused”.
Chair Steve Crocker clarified in sessions over the weekend and yesterday that it was a direction, not a request, but that the pause was merely “a moment to take stock and then get started again”.
Incoming chair Cherine Chalaby said in various sessions today and yesterday that the community — which I take to mean the leaders of the various interest groups — is now tasked with un-pausing the work.
Incoming vice-chair Chris Disspain told community leaders in an email (pdf) yesterday:

The Board has not usurped the community’s authority with respect to this review. Rather, we are asking the SOs and ACs to consider the concerns we have heard and determine whether or not adjustments are needed. We believe that a temporary pause in the SSR2 work while this consideration is under way is a sensible approach designed to ensure stakeholders can reach a common understanding on the appropriate scope and work plan

Confusion has nevertheless arise among community members, and some serious concerns and criticisms have been raised by commercial and non-commercial interests — including governments — over the last few days in Abu Dhabi.
But the board’s concerns with the work of SSR-2 seem to date back a few months, to the Johannesburg meeting in June, at which Crocker said “dangerous signals” were observed.
It’s not clear what he was referring to there, but the first serious push-back by ICANN came earlier this month, when board liaison Kaveh Ranjbar, apparently only appointed to that role in June, emailed the group to say it was over-stepping its mandate.
Basically, the SSR-2 group’s plan to carry out a detailed audit of ICANN’s internal security profile seems to have put the willies up the ICANN organization and board.
Ranjbar wrote:

The areas the Board is concerned with are areas that indeed raise important organizational information security and organizational oversight questions. However, these are also areas that are not segregated for community review, and are the responsibility of the ICANN Organization (through the CEO) to perform under the oversight of the ICANN Board.
…
While we support the community in receiving information necessary to perform a full and meaningful review over ICANN’s SSR commitments, there are portions of the more detailed “audit” plan that do not seem appropriate for in-depth investigation by the subgroup. Maintaining a plan to proceed with detailed assessments of these areas is likely to result in recommendations that are not tethered to the scope of the SSR review, and as such, may not be appropriate for Board acceptance when recommendations are issued. This also can expand the time and resources needed to perform this part of the review.

This does not seem hugely unreasonable to me. This kind of audit could be expensive, time-consuming and — knowing ICANN’s history of “glitches” — could have easily exposed all kinds of embarrassing vulnerabilities to the public domain.
Ranjbar’s letter was followed up a day later with a missive (pdf) from the chair of ICANN’s Security and Stability Advisory Committee, which said the SSR-2’s work was doomed to fail.
Patrick Falstrom recommended a “temporarily halt” to the group’s work. He wrote:

One basic problem with the SSR2 work is that the review team seems neither to have sufficient external instruction about what to study nor to have been able to formulate a clear direction for itself. Whatever the case, the Review Team has spent hundreds of hours engaged in procedural matters and almost no progress has been made on substantive matters, which in turn has damaged the goodwill and forbearance of its members, some of whom are SSAC members. We are concerned that, left to its own devices, SSR2 is on a path to almost certain failure bringing a consequential loss of credibility in the accountability processes of ICANN and its community.

Now that ICANN has actually acted upon that recommendation, there’s concern that it sets a disturbing precedent for the board taking “unilateral” action to scupper supposedly independent accountability mechanisms.
The US government itself expressed concern, during a session between the board and the Governmental Advisory Committee in Abu Dhabi today.
“This is unprecedented,” US GAC rep Ashley Heineman said. “I just don’t believe it was ever an expectation that the ICANN board would unilaterally make a decision to pause or suspend this action. And that is a matter of concern for us.”
“It would be one thing if it was the community that specifically asked for a pause or if it was a review team that says ‘Hey, we’re having issues, we need a pause.’ What’s of concern here is that ICANN asked for this pause,” she said.
UK GACer Mark Carvell added that governments have been “receiving expressions of grave concern” about the move and urged “maximum transparency” as the SSR-2 gets back on track.
Jonathan Zuck of the Innovators Network Foundation, one of the volunteers who worked on ICANN’s transition from US government oversight, also expressed concern during the public forum session yesterday.
“I think having a fundamental accountability mechanism unilaterally put on hold is something that we should be concerned about in terms of process,” he said. “I’m not convinced that it was the only way to proceed and that from a precedential standpoint it’s not best way to proceed.”
Similar concerns were voiced by many other parts of the community as they met with the ICANN board throughout today and yesterday.
The problem now is that the bylaws do not account for a board-mandated “pause” in a review team’s work, so there’s no process to “unpause” it.
ICANN seems to have got itself tangled up in a procedural quagmire — again — but sessions later in the week have been scheduled in order for the community to begin to untangle the situation.
It doubt we’ll see a resolution this week. This is likely to run for a while.

Egyptian elected new GAC chair

Manal Ismail, Egypt’s representative to ICANN’s Governmental Advisory Committee, has been elected its new chair.
She will replace outgoing chair Thomas Schneider, a Swiss official, after the current ICANN 60 public meeting in Abu Dhabi wraps up later this week.
Ismail is director of international technical coordination at Egypt’s National Telecom Regulatory Authority, NTRA.
Schneider said he was stepping down from the GAC earlier this year, having received a promotion back home that will limit his availability for ICANN work.
The handover means that both the GAC and the ICANN board of directors will, from this Thursday, be chaired by Egyptians.
The ICANN board will on Thursday formally elect current vice chair Cherine Chalaby as Steve Crocker’s replacement.
Chalaby was born in Egypt, also holds British citizenship, and lives in the United States.
I believe it’s the first time both chair roles have been held by people of the same nationality.