|
The new Community Priority Evaluation (CPE) guidelines prepared by the Economist Intelligence Unit (EIU), and published by ICANN are now past their feedback period. We, at Radix, believe that ICANN has received feedback from approximately 10 stakeholders, and I for one, am looking forward to those being published.
In light of the fact that none of the comments that ICANN received have been made public yet, I decided to blog about my multiple concerns with the new guidelines. Sparing a thought for the not-so-involved reader, I have limited my rant to some of the more important issues.
These also form the crux of our feedback submitted to ICANN along with a suggested red-lined version of the actual guidelines that can be found here.
#1: New guidelines cannot supersede the AGB
Of primary concern to us are certain communications between CTAG and ICANN, which we believe sought to modify the process and scoring guidelines in the AGB and relax the CPE standards.?
One can infer from Mr. Craig Schwartz’s recent letter to Ms. Christine Willett (VP, gTLD Operations) and correspondence on the NTAG list that a closed-door meeting was held in Durban where community TLD applicants potentially lobbied ICANN to amend the Guidebook and relax the CPE standards. ?
Hundreds of applicants have relied on the AGB and paid tens of millions of dollars in applying for specific strings. The publication of these new guidelines for feedback must not lead to a re-litigation of the Guidebook criteria. A change in the Guidebook at this stage would significantly change the rights of applicants and the value of their investments. Applicants would have made different decisions if the CPE criteria were different. ?
The CPE has been built upon a foundation of guiding principles that the community applicants seek to upset. A qualified community application eliminates all directly contending standard applications, regardless of how well qualified the latter may be. This is a fundamental reason for enforcing very stringent qualification requirements for a community-based application. It is for these reasons that we firmly believe that the AGB must be, in effect, sacrosanct.?
We believe that this concern was likely voiced by other applicants too. As a result, the CPE teleconference held on 10th September, 2013 started with Christine issuing a clarification that ICANN did not intend that the new guidelines would change anything in the AGB. We certainly hope that the intention shows up more clearly in EIU’s next draft of the guidelines.?
#2: A detailed process for the Community Priority Evaluation is still missing
The limited CPE process as defined in the current guidelines document provides for applications to be evaluated by two evaluators working independently to score applications. These will then be reviewed by members of the core project team to ensure consistency of approach across all applications.?
The process, when published, should clearly address scenarios where the evaluators and core project team members have conflicting views and specify which opinion would be binding. Additionally, there should be more detail on the documentation that will accompany each evaluation result. This, along with some clarity on how interactions between applicants and panels (public vs. private) will be managed as well as expected timelines for the complete process (incorporating the effects of GAC Advice and dispute resolution) would be a good start.
#3: Recommendations for Training and Process
ICANN and EIU must institute processes that will ensure consistency in CPE decisions.
Training: Follow-on documents from EIU should describe training and scenario testing to ensure that panels arrive at similar conclusions given identical data sets. Training should conclude when consistency is attained. Training should also include exposure to documents describing development of the community processes that include foundations in the guidebook. ICANN staff involved in the development should brief EIU panelists to describe the rationale for the current CPE standards.
Process: The process should include collaboration among panelists or evaluation of applications by the same evaluation panel (with several members) so that results are consistent. QA and other reviews should review rationale as well as scores to ensure the right scores were made for the right reasons. Rationale must be required for each score that relates to specific criteria and definitions in the Guidebook.?
Christine did mention on the CPE teleconference that scoring decisions would be accompanied with a justification for a particular score. While we find that encouraging, we can only hope that there will be consistency in the justifications provided across panels and across applications.
#4: The guidelines should be clearer and must not weaken the AGB criteria or change the application
In many cases, the new Guidelines, taken as written, seem to weaken the Guidebook criteria, either through vagueness or an inadvertent change to the intent. The new Guidelines should serve to retain the existing Guidebook criteria and provide additional clarity in a way that accomplishes the intent of the elaborate policy making process.?
While the EIU document provides additional information for evaluators, the information is vague in some places, and will undoubtedly lead to inconsistent results. An example where an explanation in the new guidelines creates uncertainty is:?
“‘Delineation’ also refers to the extent to which a community has the requisite awareness and recognition from its members.”
[How should the evaluator gauge whether a community has the “requisite awareness and recognition”?]
The use of Internet searches employed by evaluators is also of concern. Internet searches should be used only to the extent of verifying claims of the applicant. However information gathered from an Internet search should not be used towards modifying any claims/statements made in the application. It is important to limit the evaluators’ discretion in this area.
Which brings us to the next concern; the document omits significant portions of the AGB definitions and replaces them with general questions to be answered by panels. We are concerned that the EIU should not use a different standard than the published one.
Conclusion
While we are aware that the guidelines are well-intentioned, we have requested that care must be taken to ensure that the Guidebook intent is realized in the evaluation. Otherwise, the reliance placed by applicants upon the Guidebook processes and standards would have been misplaced. Those processes and standards were developed after long, intensive community discussion. Individual interests should not be allowed to change the agreed-upon implementation of the new gTLD policy at this late date. I rest my case!
Sponsored byVerisign
Sponsored byVerisign
Sponsored byIPv4.Global
Sponsored byCSC
Sponsored byRadix
Sponsored byWhoisXML API
Sponsored byDNIB.com
Shweta,
Not sure what you mean that the guidelines “weaken” the AGB. The criteria for CPE is overwhelmingly strict and the threshold is overwhelmingly high. They are unreasonably high actually.
The intent of the AGB is clear: competition, diversity and innovation. Communities play a big role in the AGB and we all agree that the ones that fulfill the goals of the program and are authentic should pass CPE (i.e to fulfill the intent of the AGB and ICANN).
All of the ICANN community agrees that ICANN has
very
strong CPE criteria and the threshold is overwhelmingly and unreasonably high enough to block any community application faking it (e.g without legitimate, demonstrable community support). There are nearly 30 community-based applicants that would be involved in CPE i.e under 4% of total applicants - a huge minority.
Concerning your “delineation” question and how it relates to the EIU guidelines I suggest you look at the GNSO recommendations (The Generic Names Supporting Organization Final Report on the Introduction of Generic New Top-Level Domains) - from which the AGB definitions are derived from (emphasis added) - offer further clarification on “Delineation” and the AGB intent on community by clearly stating that:
“Community should be interpreted broadly and will include, for example, an economic sector, a cultural community, or a linguistic community. It may be a closely related community which believes it is impacted” (http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm, Implementation Guideline P, 3).
On another issue of Delineation it is quite obvious that nearly all the supporting organizations for community applicants - which represent a significant portion of those communities - do have formal memberships in their associations and their associations represent a significant portion of those communities. In other words there is no way to game this. I also suggest you read the Community Objection case involving .Architect. No-one can deny the International Union of Architects has memberships and that the organization represents
a
significant portion of that community and that there are formal memberships for that. The Panelist agrees. Also the criteria for “delineation” in the community objections are the same as CPE pertaining to delineation. Of course I expect portfolio applicants to argue against the “delineation” point but they always seem to conveniently forget the most vital point: scoring maximum points in the CPE does
not
require “the majority” of the community but “a” (emphasis added) significant portion of the community. This is straight from the AGB. There seems to be a notion within the ICANN community that an application requires
the
majority of the community behind it (i.e more than 50%). That is impossible and is not the criteria language. The criteria is “a” significant portion. It is obvious that “a” significant portion does have formal memberships (clear and straighforward). This is consistent with the “Support” section which requires relevant institutions/supporting member organizations that are recognized and have
a
significant portion of the community as members. Consistency is key in the CPE. This pertains to the “Delineation”, “Nexus”, “Uniqueness” and “Support” sections.
To also put things in perspective, nearly all community applicants do have 1 (one) application which is restricted. Also no-one can disagree that in a case of an auction a community application would be worth less than an open application because it would not be able to have as many registrations because of its restrictions (and less registrars offering distribution for such restricted gTLDs). In other words community applicants can not compete economically speaking with an open gTLD applicant because an open applicant can afford to bid higher. Advantage portfolio applicant(s).
Community applications are important and I urge many (even those competing as open applicants) to look at the big picture and the goals of the AGB and the new gTLD program relating to competition and diversity.
It would be in the global public interest for smaller community based applicants (single string applicants) to be included in this expansion as ICANN intended it to be. Any attempts to compromise this is not in the global public interest. The internet is not all for sale and should not be all about private auctions or ICANN auctions as the sole way to determine winners because if that is the criteria then a select few will “own” most of the Internet’s most semantic words (which is where the Program is currently heading unfortunately). Also such a concept based on financial prowess alone is not one that is in the global public interest or is consistent with ICANN’s Affirmation of Commitments, especially promoting competition and diversity.
I certainly urge many to look at the big picture pertaining to this new gTLD program. I believe GAC has it right in regards to sensitive strings and certainly believe in the end CPE will award those with demonstrable community support and the appropriate policies for that respective community. How could that not be in the global public interest?
My 2 cents,
Constantine Roussos
.MUSIC (DotMusic)