Like or loathe the decision, ICANN’s new top-level domains program appears to have been delayed again.
But for how long? And what has to happen now before ICANN starts accepting applications?
In short, what the heck happened in Cartagena last week?
In this four-part post, I will attempt an analysis of the various things I think need to happen before the Applicant Guidebook (AGB) is approved.
In this second post I will look at the process problems presented by ICANN’s Governmental Advisory Committee.
The GAC Bottleneck
The main meta-story of Cartagena was ICANN’s turbulent relationship with its Governmental Advisory Committee, which is either maturing or (less likely) heading to towards a shattering collision.
The two big proposals that were widely expected to get the ICANN board’s nod last Friday – the new TLD final Applicant Guidebook and the .xxx TLD – were both delayed in whole or part by the GAC.
It’s become abundantly clear that the overall ICANN decision-making process has become subject to what I’m going to call the GAC Bottleneck.
If ICANN is serious about getting things done to its desired timetable in future, it will need to start paying attention to the GAC much earlier and much more seriously.
There’s been a failure to communicate over the last several years, the inherently problematic results of which were clearly embodied in sessions last Monday in which the GAC and the ICANN board discussed the definition of “advice”.
If there’s an “advisory” committee, and neither the committee nor the body its “advises” knows what “advice” means, that’s a pretty big stumbling block to constructive dialogue, which helps nobody.
The GAC believes that this historic uncertainty is the main reason why the new TLD program has hit an impasse at this late stage in the process.
The official Cartagena GAC Communique said:
the GAC considers that these [unresolved GAC concerns with the AGB] result primarily from the fact that the Board adopted the GNSO recommendations on new gTLDs without taking due account of GAC advice at that time, thereby creating a flawed process.
That’s pretty strong stuff – the GAC is basically saying that all the thousands of discussions the community has endured since 2007 have been carried out under faulty assumptions, because ICANN failed to pay heed to GAC advice when it was writing the rules of engagement for developing new TLD policy.
It’s also the reason we’re looking at the need for a GAC-Board retreat next February, at which ICANN will attempt to address the GAC’s outstanding concerns, before the AGB can be approved.
More on that in part three of this post.