Hi Anne and everyone,

For those unable to use Google sheets, you can insert comments on the attached excel document and send to the mailing list. Staff will add the comments to the Google sheet.

Kind regards,

Emily

From: "Aikman-Scalese, Anne" <AAikman@lrrc.com>
Date: Tuesday, 15 October 2019 at 00:43
To: Jeff Neuman <jeff.neuman@comlaude.com>, Jamie Baxter <jamie@dotgay.com>, Emily Barabas <emily.barabas@icann.org>, "gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org>
Cc: Brian Winterfeldt <Brian@Winterfeldt.law>, Heather Forrest <haforrestesq@gmail.com>, "Dean Marks (deansmarks@yahoo.com) (deansmarks@yahoo.com)" <deansmarks@yahoo.com>, "Flip Petillion (fpetillion@petillion.law)" <fpetillion@petillion.law>
Subject: [Ext] RE: CPE Supplementary Guidelines: Nexus 2-A

Thanks Jeff,

COMMUNITY PRIORITY EVALUATIONS

Regarding Community Priority Evaluations (CPE) and adopting the attached EIU guidelines for CPE evaluation for the next round, could you please remind me whether we solicited public comment on your proposal that the WG adopt the attached EIU guidelines for the next round? (Sorry – I don’t recall discussing this point system specifically in the Work Track 3 phone calls but that was a while ago.)

I agree with Jamie that the EIU Guidelines definition of “significant opposition” needs clarification. It would be good to develop some modified language about “balancing” support for and opposition against the community application as suggested on the call and as reflected by Steve Chan in the document.

It’s unclear to me how the system of “extra points” discussed on the call would work in relation to the purpose of the Community Application?

In relation to further discussion of issues from the October 10 call, I note on behalf of IPC that economic communities were expressly included in the 2012 round policy work. In order to delete the economic communities from the definition (as suggested by the Council of Europe), we would need a consensus which we do not have. So we assume that economic communities remain eligible. (This topic was also discussed in Work Track 3 calls.) Here, I think it’s important to keep in mind that some developing nations utilize economic development corporations to pull together a plan to improve their economies or regions. I don’t think anyone would want to exclude the ability of such a development corporation to be eligible for a community priority evaluation. Oftentimes these development corporations can be formed after natural disasters such as floods or hurricanes in order to promote funding and redevelopment efforts. Further, keeping the eligibility for economic communities supports the new gTLD Principle of Applicant Freedom of Expression.

APPEAL RIGHTS IN RELATION TO ICANN ORG DECISIONS, THIRD PARTY EVALUATIONS, OBJECTION PANEL RULINGS, AND COMMUNITY PRIORITY EVALUATION DETERMINATIONS

Regarding the appeals chart at the link below, it’s not clear how to register comments. Can you please clarify? (Internal guidelines do not permit me to log in to a Google document.) Since we cannot edit the document, where and how do we enter our comments?

Appeals Chart: https://docs.google.com/spreadsheets/d/1R4eU7C-HI5ikF5RtVhp5JRXKVVRn6R8WX8fIU0IOwu8/edit#gid=0 [docs.google.com]

Second Question: Regarding the possible appeal of a CPE determination, are we saying that those with standing to contest that initial CPE determination and file an appeal (either way) would be in a position to lodge a point-by-point challenge to the exact number of points given or not given in connection with the EIU guidelines for scoring as shown in the attachment? (I just need to know this in order to review with IPC.) So, by way of example, say I’m in a string contention set with a CPE application and that application is awarded community status and I then argue that for each of the ten subcriteria in the EIU guidelines, the alleged Community should have been given fewer points or 0 points than it actually received. Is that the type of appeal we are contemplating? And isn’t it likely that the CPE would ALWAYS be challenged by any competing applications that were not community based? How would “extra points” given in relation to the purpose of the Community Application be weighed in the appeals process?

Thank you,

Anne

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Jeff Neuman
Sent: Monday, October 14, 2019 1:54 PM
To: Jamie Baxter <jamie@dotgay.com>; 'Emily Barabas' <emily.barabas@icann.org>; gnso-newgtld-wg@icann.org
Subject: [Gnso-newgtld-wg] CPE Supplementary Guidelines: Nexus 2-A

[EXTERNAL]

Here is the information for Category 2-A Nexus from the FTI Review Report. Let us know if wording needs to change.

Nexus: Category 2-A

To receive a partial score of two points for Nexus,¹²⁹ the applied-for string must identify the community. According to the Applicant Guidebook, "'Identify' means that the applied-for string closely describes the community or the community members, without over-reaching substantially beyond the community."¹³⁰ In order to receive the maximum score of three points, the applied-for string must: (i) "identify" the community; and (ii) match the name of the community or be a well-known short-form or abbreviation of the community.

FTI observed that the CPE Provider determined that the applications underlying 19 CPE reports received zero points for the Nexus sub-criterion because, in the CPE Provider's determination, the applications failed to satisfy both of the requirements described above. First, for the applications underlying 11 of the 19 CPE reports that recorded zero points for the Nexus sub-criterion, the CPE Provider determined that the appliedfor string did not identify the community because it substantially overreached the community as defined in the application by indicating a wider or related community of which the applicant is a part but is not specific to the applicant's community.^{131, 132}

Second, for the applications underlying eight of the 19 CPE reports that recorded zero points for the Nexus sub-criterion, the CPE Provider found that the applied-for string did not match the name of the community or was not a well-known short form or abbreviation. In this regard, the CPE Provider determined that, although the string identified the name of the core community members, it failed to match or identify the peripheral industries and entities included in the definition of the community set forth in the application. Therefore, there was a misalignment between the proposed string and the proposed community.¹³³ In several cases, the CPE Provider's conclusion that the string did not identify the entire community was the consequence of the CPE Provider's finding that the proposed community was not clearly delineated because it described a dispersed or unbound group of persons or entities.134 Without a clearly delineated community, the CPE Provider concluded that the one-word string could not adequately identify the community.

Five CPE reports recorded two points for the Nexus sub-criterion.¹³⁵ FTI observed that these CPE reports recorded partial points because the CPE Provider determined that the underlying applications satisfied only the two-point requirement for Nexus: the applied-for string must identify the community.¹³⁶ The CPE Provider determined that, although the applied-for string identified the proposed community as defined in the application, it did not "match" the name of the community nor constitute a well-known short-form or abbreviation of the community name.¹³⁷ Specifically, the CPE Provider concluded that, for the applications underlying these five CPE reports, the community definition encompassed individuals or entities that were tangentially related to the proposed community as defined in the application and therefore, the general public may not necessarily associate all of the members of the defined community with the string.¹³⁸ Thus, for these applications, there was no "established name" for the applied-for string to match, as required by the Applicant Guidebook for a full score on Nexus.139 For all CPE reports that did not record the full three points for the Nexus sub-criterion, the CPE Provider's rationale was based on the definition of the community as defined in the application.¹³⁹

Two CPE reports recorded the full three points for the Nexus sub-criterion.¹⁴⁰The CPE Provider determined that the applied-for string in the applications underlying these two CPE reports was closely aligned with the community as defined in the application,¹⁴¹ and/or was the established name by which the community is commonly known by others.¹⁴²

¹²⁹ The Applicant Guidebook does not provide for one point to be awarded for the Nexus sub-criterion. An application only may receive two points or three points for the Nexus sub-criterion.

¹³⁰ Applicant Guidebook, Module 4.2.3 at Pg. 4-13 (https://newgtlds.icann.org/en/applicants/agb/stringcontention-procedures-04jun12-en.pdf [newgtlds.icann.org]).

¹³² See Applicant Guidebook, Module 4.2.3 Criterion 2 definitions and Criterion 2 guidelines at Pg. 4-13 (https://newgtlds.icann.org/en/applicants/agb/string-contention-procedures-04jun12-en.pdf [newgtlds.icann.org]).

¹³³ GMBH CPE Report (https://www.icann.org/sites/default/files/tlds/gmbh/gmbh-cpe-1-1273-63351- [icann.org] en.pdf) ("While the string identifies the name of the core community members (i.e. companies with the legal form of a GmbH), it does not match or identify the regulatory authorities, courts and other institutions that are included in the definition of the community as described in Criterion 1-A."); TAXI CPE Report (https://www.icann.org/sites/default/files/tlds/taxi/taxi-cpe-1-1025-18840-en.pdf [icann.org]) (where community is defined to include tangentially related industries, applied-for string name of "TAXI" fails to match or identify the peripheral industries and entities that are included in the defined community); IMMO CPE Report (https://www.icann.org/sites/default/files/tlds/immo/immo-cpe-1-1000-62742-en.pdf [icann.org]) (applied for string identifies only the name of the core community members (primary and secondary real estate members), but fails to identify peripheral industries and entities described as part of the community by the applicant and does not match the defined community); ART (Dadotart) CPE Report (https://www.icann.org/sites/default/files/tlds/art/art-cpe-1-1097-20833-en.pdf [icann.org]) ("While the string identifies the name of the core community members (i.e. artists and organized members of the arts community) it does not match or identify the art supporters that are included in the definition of the community as described in Criterion 1-A" such as "audiences, consumers, and donors"); KIDS CPE Report (https://www.icann.org/sites/default/files/tlds/kids/kids-cpe-1-1309-46695-en.pdf [icann.org]) (concluding that although applied-for string identifies the core community members—kids—it fails to closely describe other community members such as parents, who are not commonly known as "kids"); MUSIC (.music LLC) CPE Report (https://www.icann.org/sites/default/files/tlds/music/music-cpe-1-959-51046-en.pdf [icann.org]) (applied for string is over inclusive, identifying more individuals than are included in the defined community); GAY CPE Report (https://www.icann.org/sites/default/files/tlds/gay/gay-cpe-1-1713-23699-en.pdf [icann.org]) (the applied for string refers to a large group of individuals – all gay people worldwide – of which the community as defined by the applicant is only a part); and GAY 2 CPE Report (https://www.icann.org/sites/default/files/tlds/gay/gay-cpe-rr-1-1713-23699-en.pdf [icann.org]) (applied-for string "GAY" is commonly used to refer to men and women who identify as homosexual but not necessarily to others in the defined community).

¹³⁴ See, e.g., KIDS CPE Report (https://www.icann.org/sites/default/files/tlds/kids/kids-cpe-1-1309- [icann.org] 46695-en.pdf); ART (Dadotart) CPE Report (https://www.icann.org/sites/default/files/tlds/art/art-cpe-1- [icann.org] 1097-20833-en.pdf); and IMMO CPE Report (https://www.icann.org/sites/default/files/tlds/immo/immocpe-1-1000-62742-en.pdf [icann.org]).

¹³⁵ HOTEL CPE Report (https://www.icann.org/sites/default/files/tlds/hotel/hotel-cpe-1-1032-95136- [icann.org] en.pdf); ART (eflux) CPE Report (https://www.icann.org/sites/default/files/tlds/art/art-cpe-1-1675-51302- [icann.org] en.pdf) ECO CPE Report (https://www.icann.org/sites/default/files/tlds/eco/eco-cpe-1-912-59314-en.pdf [icann.org]); MUSIC (DotMusic Ltd.) CPE Report (https://www.icann.org/sites/default/files/tlds/music/music-cpe-1- [icann.org] 1115-14110-en.pdf); and RADIO CPE Report (https://www.icann.org/sites/default/files/tlds/radio/radiocpe-1-1083-39123-en.pdf [icann.org]).

¹³⁶Applicant Guidebook, Module 4.2.3 at Pgs. 4-12-4-13 (https://newgtlds.icann.org/en/applicants/agb/string-contention-procedures-04jun12-en.pdf [newgtlds.icann.org]).

¹³⁷ See, e.g., ECO CPE Report (https://www.icann.org/sites/default/files/tlds/eco/eco-cpe-1-912-59314- [icann.org] en.pdf) (concluding that string "ECO" identifies community of environmentally responsible organizations, but is not a match or well-known name because the various organizations in the defined community are generally identified by use of the word "environment" or by words related to "eco" but not by "eco" itself or on its own).

¹³⁸ HOTEL CPE Report (https://www.icann.org/sites/default/files/tlds/hotel/hotel-cpe-1-1032-95136- [icann.org] en.pdf) (applied-for string "HOTEL" identifies core members of the defined community but is not a wellknown name for other members of the community such as hotel marketing associations that are only related to hotels); MUSIC (DotMusic Ltd.) CPE Report (https://www.icann.org/sites/default/files/tlds/music/music-cpe-1-1115-14110-en.pdf [icann.org]) (concluding that because the community defined in the application is a collection of many categories of individuals and organizations, there is no "established name" for the applied-for string to match, as required by the Applicant Guidebook for a full score on Nexus, but that partial points may be awarded because the string "MUSIC" identifies all member categories, and successfully identifies the individuals and organizations included in the applicant's defined community); ECO CPE Report (https://www.icann.org/sites/default/files/tlds/eco/eco-cpe-1-912-59314-en.pdf [icann.org]) (concluding that string "ECO" identifies community of environmentally responsible organizations, but is not a match or wellknown name because the various organizations in the defined community are generally identified by use of the word "environment" or by words related to "eco" but not by "eco" itself or on its own); ART (eflux) CPE Report (https://www.icann.org/sites/default/files/tlds/art/art-cpe-1-1675-51302-en.pdf [icann.org]) (applied-for string "ART" identifies defined community, but, given the subjective meaning of what constitutes art, general public may not associate all members of the broadly defined community with the applied-for string); and RADIO CPE Report (https://www.icann.org/sites/default/files/tlds/radio/radio-cpe-1-1083- [icann.org] 39123-en.pdf) (applied-for string "RADIO" identifies core members of the defined community but is not a well-known name for other members of the community such as companies providing specific services that are only related to radio).

¹³⁹ See, e.g., MUSIC (DotMusic Limited) CPE Report ( https://www.icann.org/sites/default/files/tlds/music/music-cpe-1-1115-14110-en.pdf [icann.org]).

¹⁴⁰ OSAKA CPE Report (https://www.icann.org/sites/default/files/tlds/osaka/osaka-cpe-1-901-9391- [icann.org] en.pdf); and SPA CPE Report (https://www.icann.org/sites/default/files/tlds/spa/spa-cpe-1-1309-81322- [icann.org] en.pdf).

¹⁴¹ SPA CPE Report at Pg. 4 (https://www.icann.org/sites/default/files/tlds/spa/spa-cpe-1-1309-81322- [icann.org] en.pdf); and OSAKA CPE Report at Pgs. 3-4 (https://www.icann.org/sites/default/files/tlds/osaka/osakacpe-1-901-9391-en.pdf [icann.org]).

¹⁴² SPA CPE Report at Pgs. 4-5 (https://www.icann.org/sites/default/files/tlds/spa/spa-cpe-1-1309- [icann.org] 81322-en.pdf).

Jeff Neuman

Senior Vice President

Com Laude | Valideus

D: +1.703.635.7514

E: jeff.neuman@comlaude.com

From: Jamie Baxter <jamie@dotgay.com>
Sent: Friday, October 11, 2019 12:41 PM
To: Jeff Neuman <jeff.neuman@comlaude.com>; 'Emily Barabas' <emily.barabas@icann.org>; gnso-newgtld-wg@icann.org
Subject: RE: [Gnso-newgtld-wg] Community Priority Evaluations Review of Supplementary Guidelines

Good afternoon Working Group members

On the last call regarding Community Applications, everyone was asked to review the EIU’s CPE Guidelines to see if there are any items that need further scrutiny before being added into the AGB for subsequent procedures.

My apologies for the length of this response, but hopefully these notes help provide insight on how the AGB language was interpreted from a Community Applicant perspective, and what things continue to need further clarification before the next AGB is published.

1-A Delineation

Page 4: “Delineation”

The non-exhaustive list the EIU added into the CPE guidelines that denotes elements of straight-forward member definitions contains a clear bias towards professional and trade communities. The AGB did not carry this kind of bias, and it would be a concern if the next AGB projected this kind of bias around delineation, especially since many linguistic and cultural communities are straight-forward in the eyes of their members but do not use a membership card system.

Can review be done to determine what other forms of delineation were accepted in CPE scoring from all community applications in the 2012 round? And can those examples be included in the examples already noted by the EIU?

2-A Nexus

“Identify”

The AGB very clearly states that “”identify” means that the applied for string closely describes the community or the community members,” providing two distinct paths to establish if an applied for string identifies the community. These paths are not interconnected or contingent on one another in the AGB, but instead suggest separate routes to establishing nexus.

My interpretation of this AGB language is that an applicant can select a string that is a known identifier of the community, or a string that identifies the specific members of that community. Additionally, no rule is placed on the “known identifier of the community” as needing to be the only identifier of that community.

The AGB additionally provides two examples to help illustrate the definition of “identity” for each of the possible paths.

As an example, a string could qualify for a score of 2 if it is a noun that the typical community member would naturally be called in the context. (AGB, Pg 197)
If the string appears excessively broad (such as, for example, a globally well-known but local tennis club applying for “.TENNIS”) then it would not qualify for a 2. (AGB, Pg 197)

What the AGB does not do with these examples is suggest that both paths must be successfully maneuvered in order to achieve 2 points. The definition of “identify” in the AGB suggests the applicant had the choice to design their application around a name of the community (TENNIS community), or the member attributes in the community (TENNIS players, TENNIS coaches, etc).

This is clearly noted in example 1 where 2 points were achieved when it’s confirmed the string identifies the actual community members. The second example denying 2 points for .TENNIS however does not further elaborate on how 2 points could have been achieved in the case of describing the TENNIS community.

The second example could suggest that if an internationally recognized tennis club applied for .TENNIS instead of a local tennis club, for use among those in the wider TENNIS community (broadcasters, networks, physical therapists, vendors, fans, etc – all tertiary parts of the community that also have other identifiers), then it could have been successful on the path of “closely describes the community.” When the average person thinks of the TENNIS community they could reasonably include the list above, yet these participants in the TENNIS community may not identify naturally with the word TENNIS (i.e. a tennis broadcaster that also covers football).

Although the EIU’s CPE guidelines are silent on establishing further clarity around the AGB language related to the two paths to “identify,” the practice of the EIU did not align with the flexibility of the AGB. The EIU appears to have conflated the two distinct paths as one and made them both requirements under the definition of “identity,” or at least imposed the requirement that the string be a term the community members naturally call themselves. This may have happened because the two examples outlined above run sequentially in the AGB, causing confusion without distinction.

Given the unfortunate implementation route taken by the EIU, it should be more clear in the AGB what is meant by “identify means that the applied for string closely describes the community or the community members.” I believe it offers two separate paths to success for community applicants, one based on a widely used and identifiable name of the community (known by those inside & outside the community) and the other based on the identity of the actual members in the community.

4-B Opposition

“Relevance”

As discussed on the last call, guidance for “relevance” in 4-B must include a balance of opposition in relation to documented support, and not just an isolated determination of whether the opposing entity is part of the community explicitly or implicitly addressed. One misaligned community member/entity should not have the power to impact CPE scores of a largely aligned community, yet that was the EIU’s interpretation and practice in the 2012 round.

To illustrate this point, if an applicant has hundreds of organizations from around the world supporting an application, and those endorsements represent the voices of tens of thousands of other local and regional organizations, then an expression of opposition from one single, small and even locally based organization from within the defined community among the thousands globally expressing support should not be able to put 1 of the 2 CPE points for this criteria in jeopardy.

Cheers

Jamie

Jamie Baxter

dotgay LLC

jamie@dotgay.com

www.dotgay.com [dotgay.com]

A Certified LGBT Business Enterprise (LGBTBE)

Please join us on Facebook at www.facebook.dotgay.com [facebook.dotgay.com]

and follow us at www.twitter.com/dotgay [twitter.com]

From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Jeff Neuman
Sent: Thursday, October 10, 2019 2:54 PM
To: Emily Barabas; gnso-newgtld-wg@icann.org
Subject: [Gnso-newgtld-wg] Community Priority Evaluations Review of Supplementary Guidelines

All,

I would hope that everyone reads all of the notes sent out on each of the meetings carefully, but just in case, I want to draw your attention to one of the biggest action items that arose as a result of our call this morning (Wednesday night for those in the US). In addition, I would like to pose a question for consideration by the Working Group.

“ACTION ITEM: WG members will go through the guidelines and flag anything they think should not be incorporated into the AGB for subsequent procedures. See guidelines at: https://newgtlds.icann.org/en/applicants/cpe/guidelines-27sep13-en.pdf [newgtlds.icann.org]”

One of the universal criticisms about the CPE process was that there were additional rules and guidelines that were adopted by the CPE Evaluators (EIU) after all of the applications were submitted. The Working Group will most likely be recommending that all rules be set forth in the Applicant Guidebook or at the very latest prior to the Application Window opening up. That message has been delivered loud and clear.

Something that can help, however, would be if the Working Group could review the CPE Guidelines that were developed by EIU (at the link above) to see if those Guidelines make sense and whether those Guidelines or something similar to those Guidelines could be formally adopted as part of our recommendations. Putting aside the fact that these came after applications were submitted, many of the Guidelines make sense. If we formally approve them, then this will go a long way to helping potential applicants understand how CPE evaluations will work.

Clarifying Questions and CPE: A second item which looks likely to be a recommendation will be that CPE Evaluators should utilize the CQ process (Clarification Questions process) to seek clarifications (but not new material) from the applicant on items where it has questions or issues. However, would it also be advisable for the CPE Evaluators to be able to send CQs to those that oppose a community application (and that have submitted letters of opposition)? In other words, CPE Evaluators can ask those that oppose the application questions about themselves and how representative they are. They can drill down on details about what it is that they oppose, etc. Those on the call thought this may be a good idea to help weed out frivolous letters of opposition or also emphasize the opposition of real entities, persons and communities.

We believe these should be non-controversial, but would like to input other than that which we got on the call.

Best regards,

Jeff Neuman

Senior Vice President

Com Laude | Valideus

D: +1.703.635.7514

E: jeff.neuman@comlaude.com

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Emily Barabas
Sent: Thursday, October 10, 2019 7:16 AM
To: gnso-newgtld-wg@icann.org
Subject: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 10 October 2019

Dear Working Group members,

Please see below the notes from the meeting on 10 October 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-10-10+New+gTLD+Subsequent+Procedures+PDP.

On the call, it was suggested that guidelines used by CPE evaluators in the 2012 round should be incorporated into the Applicant Guidebook in subsequent procedures to improve predictability. Please see the notes below for details. As a follow up to the action item below, WG members are encouraged to review the 2012 CPE guidelines (https://newgtlds.icann.org/en/applicants/cpe/guidelines-27sep13-en.pdf [newgtlds.icann.org]) and raise on the mailing list if there are elements of the guidelines that they believe should not be incorporated into the AGB.

Kind regards,

Emily

Notes and Action Items:

Action Item:

ACTION ITEM: WG members will go through the guidelines and flag anything they think should not be incorporated into the AGB for subsequent procedures. See guidelines at: https://newgtlds.icann.org/en/applicants/cpe/guidelines-27sep13-en.pdf [newgtlds.icann.org]

Notes:

1. Welcome and Update to Statements of Interest

No SOI updates

Following up on Monday’s call, there is a revised chart available on appeals. Please add questions and comments to the draft for discussion on the email list. The chart is available at: https://docs.google.com/spreadsheets/d/1R4eU7C-HI5ikF5RtVhp5JRXKVVRn6R8WX8fIU0IOwu8/edit?usp=sharing [docs.google.com]

2.a. Community Applications

Policy Goals are high-level and non-controversial. High-Level agreements so far: The Community Priority Evaluation (CPE) process must be more transparent and predictable; All evaluation procedures should be developed BEFORE the application process opens and made easily and readily available.
CCT-RT Recommendation 34 also suggests making improvements to address concerns raised about community applications before going forward with subsequent procedures.
Guidelines developed by the evaluators have not been discussed in depth by this group, other than the fact that they were made available late in the process. Key point raised in the public comments -- information contained in the guidelines needs to be available to applicants before applications are submitted.
Would it make sense to put some of the guidelines developed by the evaluators into the Applicant Guidebook?
Were there things in the guidelines, other than those detailed in the public comments, which were problematic?
ACTION ITEM: WG members will go through the guidelines and flag anything they think should not be incorporated into the AGB for subsequent procedures. See guidelines at: https://newgtlds.icann.org/en/applicants/cpe/guidelines-27sep13-en.pdf [newgtlds.icann.org]
By including guidelines in the AGB, there would be greater predictability for applicants and also greater clarity for future evaluators.
As a community applicant, there was a lot left open for interpretation in the 2012 AGB. As a result, an applicant’s interpretation of the guidebook may have been different from what the evaluators took away when they developed their guidelines. This resulted in a discrepancy that should not exist in subsequent procedures.
Review of suggestions in the public comments on improving transparency and predictability of the CPE process.
Review of comments on the definition of community.
One WG member disagrees with the way the EIU further restricted the definition of community in its guidelines, and suggests that this is not incorporated into the AGB going forward. Specifically, the EIU prioritized those that had a structured system to the community -- institutionalized or industry-related organizations would therefore be higher priority.
Suggestion - what if ICANN community members served as CPE panelists? They might better understand the definition of community from the ICANN perspective. ALAC advised in their public comments that members of grassroots organizations should serve as panelists.
Response - Different members of the ICANN community might understand the definition differently. ICANN never provided a clear definition. ICANN was relying on the scoring to delineate who should get priority rather than having a specific definition.
In selecting an entity to do the evaluations, ICANN was looking for expertise in doing this type of evaluation with independence, but as a result the evaluators may not have as much perspective on what ICANN was trying to achieve. Members of the ICANN community come in with their own biases. Could community members perhaps have some kind of advisory role instead?
The choice of evaluators may have impacted the way they approached the evaluation process. EIU has an economic focus.
Further review of suggestions for improving transparency and predictability of the CPE process in relation to the preliminary recommendation that the CPE process must be more transparent and predictable.
Conflict of interest provisions discussed previously should be applicable to all panelists, including those conducting CPE. This will address public comments that raised concerns about conflict of interest.
Comment - it is very important that one “naysayer” does not prevent an application from moving forward. There needs to be substantial opposition.
Suggestion for an additional WG Recommendation: If there was research relied on for the decision it should be cited and a link to the information provided. This is based on comments from Jaime Baxter, ALAC, and NCSG.
Some have commented that the costs of the process should be lower and that the process should be quicker. Suggestion for an implementation note stating ICANN staff should examine ways to make the process more efficient in terms of cost and timing. It may be difficult to be more detailed since ICANN Org is in the best position to evaluate how to increase efficiencies.
Comment - At this stage, ICANN Org should be better able to scope the task with a service provider and set clear expectations. The service provider should be responsible for remaining within budget.
Review of public comments on preliminary recommendation: CPE evaluations should be completed in a shorter period of time.
Review of public comments on preliminary recommendation: All evaluation procedures should be developed BEFORE the application process opens and made easily and readily available.
Review of public comments on preliminary recommendation: The CPE process should include a process for evaluators to ask clarifying questions and where appropriate engage in a dialogue with the applicant [and providers of letters of opposition?] during the CPE process. ICANN org raised concerns about potential lobbying and lack of transparency that could result from this type of engagement. Perhaps panelists could ask clarifying questions in written format --- all materials would be publicly available. The opportunity would be equally available to all parties to ensure that the process is fair.
Preliminary Recommendation about dialogue between evaluators and relevant parties will be revised and included as a draft recommendation for the WG to consider further.
One WG member stated that community applicants can’t change their application, and that the opportunity for dialogue won’t change the application. It simply provides an opportunity for the applicant to illustrate key points so that the evaluators understand the application. There is little room for lobbying from this perspective.
Response -- by putting everything in writing, there is still this opportunity to clarify, and there is greater transparency.
Additional question - should the panelists be able to send clarification questions to those filing opposition letters? One member expressed support for this proposal. It may help to bring greater clarity to understanding the legitimacy of the opposition. It’s important to be clear that this is not about community-based objections but about opposition to community-based applications.
Review of public comments on preliminary recommendation: Less restrictive word count for communities to engage in clarifying and providing information. ALAC expressed opposition to this recommendation.
It may be helpful to do some additional research on the existing word count restrictions, but there did not seem to be much support for increasing limits on word count.
Review of ALAC comment on providing access to experts to assist communities, particularly those from underserved regions in preparing applications in order to level the playing field. Suggestion to link this comment to the topic Applicant Support.
Review of comments on potentially providing alternative benefits if an applicant scored below the threshold.
Review of suggested changes to evaluation criteria or weight/scoring of criteria -- in particular, discussion of the comment that if opposition is expressed, it must be examined in the big picture and weighed against the volume of support. There should be a balance.
Discussion of suggestion in the public comments that there should be addition criteria around benefit to registrants -- perhaps there could be a form of “extra credit” granted to applicants that help or solve a problem inside a community. This could come in the form of bonus points. It might address some of the public comments from the Council of Europe, as well.
Clarification - this is already a requirement of the application, however it was not translated into the scoring criteria. It was incorporated into the contract as a commitment to the community. It would make sense for this to part of the scoring criteria.
Review of comments on whether there should continue to be preferential treatment for community applications -- there is general support for this concept. NCSG expressed concern about the definition of community. Registrars would like to eliminate the concept of community.
Review of comments on the Council of Europe report.
Review of comments in response to the question - to what extent should evaluators be able to deviate from pre-published guidance and guidelines?
Additional comment raised by a WG member -- any requirements about letters of support should be clear and transparent up front.
Review of additional considerations on selection of panelists and program goals raised by the Council of Europe.
Note that ICANN is currently examining the concept of Global Public Interest which may be responsive to the Council of Europe’s comments on this topic.

3. AOB

None.

The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see www.comlaude.com [comlaude.com]

[avast.com]

Virus-free. www.avast.com [avast.com]

This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.