<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Hi Evan,</p>
<p><br>
</p>
<p>The Council of Europe has produced a report that is pretty critical of how Community Based Applications were dealt with in the 2012 round. It presents recommendations for subsequent new gTLD procerdures, if any:
<a href="https://rm.coe.int/16806b5a14" class="OWAAutoLink" id="LPlnk93531" previewremoved="true">
https://rm.coe.int/16806b5a14</a></p>
<p><br>
</p>
<p>The report has been preliminarily discussed at recent joint ALAC/GAC meetings, and the UK GAC delegate Mark Carwell is now preparing a paper on it for consideration by the GAC. There's an idea of inviting him to an ALAC meeting to talk about it, and to search
for common ground on this issue between our AC's.</p>
<p><br>
</p>
<p>I agree with you that this issue could be a big one for At-Large. It could be an even bigger one for a joint ALAC/GAC démarche.
<br>
</p>
<p><br>
</p>
<p>Best,</p>
<p><br>
</p>
<p>Yrjö<br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block; width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> alac-bounces@atlarge-lists.icann.org <alac-bounces@atlarge-lists.icann.org> on behalf of Evan Leibovitch <evan@telly.org><br>
<b>Sent:</b> Tuesday, September 5, 2017 9:23 PM<br>
<b>To:</b> ICANN At-Large Staff<br>
<b>Cc:</b> ICANN ALAC list<br>
<b>Subject:</b> Re: [ALAC] [ALAC-Announce] ICANN News Alert -- ICANN Provides Update on Review of the Community Priority Evaluation Process</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">Given that this issue (the way communities were evaluated -- and in the view of At-Large, mostly unfairly rejected) is big one for At-Large. why is the review being done by outside
consultants and not the community?<br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">I would like to flag this -- the treatment of communities in the allocation of gTLDs -- as a major At-Large issue should ICANN be foolish enough to engage in more rounds. Perhaps
it is worth the effort of the community to draft a comment, using the work of this Review and the existing community efforts to engage in new rounds of gTLD allocations, as a catalyst from which we may draft a coherent high-level ALAC policy on the issue.
Once created, this policy can/should take form of Formal Advice to the Board, which is still ALAC's primary (and only bylaw-mandated) channel to make itself heard.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">In a recent post I referred to the too-frequent practice of being distracted by the trivial while major issues of concern -- that are more complex and difficult for reaching consensus
-- are bypassed. I would like to suggest that this issue -- the treatment of communities -- become one of the primary concerns of At-Large should ICANN consider further namespace expansion. We have a number of case studies -- .music, .gay, .kids among them
-- as clear communities that were denied (or cheated, depending on opinion) out of the ability to apply. The problem with community evaluation also completely rendered useless the Applicant Support Program that At-Large and the GAC championed in the last round.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">I offer to help draft such a policy but I won't do it alone. There must be broader desire within the community for this than one person, should this issue be given the weight of
authority that IMO it needs. But I am happy to coordinate and add what I can.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">- Evan</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 5 September 2017 at 13:54, ICANN At-Large Staff <span dir="ltr">
<<a href="mailto:staff@atlarge.icann.org" target="_blank">staff@atlarge.icann.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div bgcolor="white" lang="EN-US">
<div class="m_5287835676073340237WordSection1">
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:solid #cccccc 1.0pt; padding:8.0pt 8.0pt 8.0pt 8.0pt">
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=6RvSzjTvjB7S1VSBjP6ihfBO5ryNhTuEVsj102jJfy4&e=" target="_blank"><span style="text-decoration:none"><img id="m_5287835676073340237_x0000_i1025" alt="CANN" width="94" border="0" height="94" src="https://www.icann.org/sites/default/files/assets/icann-primary-94x94.jpg"></span>[icann.org]</a>
<u></u><u></u></p>
<h2>News Alert<u></u><u></u></h2>
<p style="margin-right:0in; margin-bottom:7.5pt; margin-left:0in"><span style="font-size:12.0pt; font-family:"Arial",sans-serif"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D09-2D01-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=AEcTVM6uqbZyGV3iSJc_E42sDIWYp5EXRja_fHGMFqE&e=" target="_blank">https://www.icann.org/news/<wbr>announcement-2017-09-01-en[<wbr>icann.org]</a><u></u><u></u></span></p>
<div class="MsoNormal" style="margin-top:15.0pt; text-align:center" align="center">
<hr width="100%" size="2" align="center">
</div>
<h2 style="margin-bottom:0in; margin-bottom:.0001pt">ICANN Provides Update on Review of the Community Priority Evaluation Process
<u></u><u></u></h2>
<p>LOS ANGELES – 1 September 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today issued an
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_cpe&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=qNE6yYTV2JqbDi_y0nUWZkDcHov-bQY-sCkYJGxlTM4&e=" target="_blank">
update[newgtlds.icann.org]</a> on the review of the Community Priority Evaluation (CPE) process.<u></u><u></u></p>
<p>Community Priority Evaluation is a method to resolve string contention, described in full detail in section 4.2 of the
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_agb&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=y5onXHYzQc_RdrOkrk2OFAxJJsMtyKaV4st0alTBkiw&e=" target="_blank">
Applicant Guidebook (AGB)[newgtlds.icann.org]</a>. The evaluation determines if the community based application qualifies to earn priority and eliminate all non-community applicants in the contention set as well as any other non-prevailing community applicants.
In CPE, the application is evaluated against the following four criteria: Community Establishment; Nexus between Proposed String and Community; Registration Policies, and Community Endorsement. The evaluations were conducted by the Economist Intelligence Unit
(EIU). The EIU was selected for this role because it offers premier business intelligence services, providing political, economic, and public policy analysis to businesses, governments, and organizations across the globe.<u></u><u></u></p>
<p>At various times in the implementation of the New gTLD Program, the ICANN Board has considered aspects of CPE process, including certain concerns that some applicants have raised regarding the process. On
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_board-2Dmaterial_resolutions-2D2016-2D09-2D17-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=b_66o8gDzKo-vDAFpzh7zfJ9i2kZZEuTDHhiWn0ORU0&e=" target="_blank">
17 September 2016[icann.org]</a>, the ICANN Board directed the President and CEO, or his designees, to undertake a review of the process by which ICANN has interacted with the CPE provider. In his
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_disspain-2Dletter-2Dreview-2Dnew-2Dgtld-2Dcpe-2Dprocess-2D26apr17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=tccQoHoyUd_tO3vDdnSUKdo8LjIUfgrnpzNj6HMAffQ&e=" target="_blank">
letter of 26 April 2017 to concerned parties[icann.org]</a> [PDF, 405 KB], Chris Disspain, the Chair of the Board Governance Committee, provided additional information about the scope and status of the review. Below is additional information about the review,
as well as the current status of the CPE process review. On <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_cpe_process-2Dreview-2Dupdate-2D02jun17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=8_2bJs86sdpIGh-d0eCBKLOV7gGDSJmICeCVwDqJseQ&e=" target="_blank">
2 June 2017[newgtlds.icann.org]</a>, the ICANN organization published an update on the Review.<u></u><u></u></p>
<p>Below is the current status of the Review since the last update.<u></u><u></u></p>
<h3>Current Status of the Review<u></u><u></u></h3>
<p>The <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_cpe_process-2Dreview-2Dupdate-2D02jun17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=8_2bJs86sdpIGh-d0eCBKLOV7gGDSJmICeCVwDqJseQ&e=" target="_blank">
2 June 2017 update[newgtlds.icann.org]</a> made clear that the Review is being conducted in two parallel tracks by
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fticonsulting.com_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=I-apoKOnojHdSns9QteKkMx5qKJRheOfoIMm93UTNBk&e=" target="_blank">
FTI Consulting Inc.’s (FTI)[fticonsulting.com]</a> Global Risk and Investigations Practice (GRIP) and Technology Practice. The work of the first track, which focuses on gathering information and materials from the ICANN organization, has been completed. The
work of the second track, which focuses on gathering information and materials from the CPE provider, is still ongoing. The interview process of the CPE provider personnel that had involvement in CPEs has been completed. FTI is also working with the CPE provider
to obtain the reference materials for the evaluations that are the subject of pending
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_accountability_reconsideration-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=D09yejutJd7LYkn0UUvUmuobp8S0Xwq-IPc0iRnaBVE&e=" target="_blank">
Reconsideration Requests[icann.org]</a>. The CPE provider has been producing documents on a rolling basis. FTI is currently evaluating whether the CPE provider’s production is complete. Once the underlying information and data collection is complete, FTI anticipates
that it will be able to inform ICANN of its findings within two weeks.<u></u><u></u></p>
<p>Recently, the ICANN Board and the ICANN organization have received numerous inquiries for documentation and information about the Review. These inquiries have been and will continue to be addressed through ICANN’s Documentary Information Disclosure Policy
(DIDP), and are published on the DIDP page at <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_governance_transparency-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=LvjRu0jhlL3LCs471CQqtJ2nK-iOlhE8BAW4yZ99NKo&e=" target="_blank">
https://www.icann.org/<wbr>resources/pages/governance/<wbr>transparency-en[icann.org]</a>.<u></u><u></u></p>
<p>The ICANN Board recognizes the desire by many to conclude this Review and proceed with the process. The ICANN Board also looks forward to concluding the Review and proceeding as appropriate.<u></u><u></u></p>
<p>For more information about the CPE process, please visit <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_cpe&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=xzfqc9z84D1KNQBHM_8mQtANhQCeSWynaCwxY1BH8YE&s=qNE6yYTV2JqbDi_y0nUWZkDcHov-bQY-sCkYJGxlTM4&e=" target="_blank">
https://newgtlds.icann.org/en/<wbr>applicants/cpe[newgtlds.icann.<wbr>org]</a>.<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal" style="text-align:center" align="center"><img id="m_5287835676073340237_x0000_i1028" width="1" border="0" height="1" src="http://click.icptrack.com/icp/track.php?msgid=1009048&act=CWP8&r=28876652&c=165637"><u></u><u></u></p>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
ALAC-Announce mailing list<br>
<a href="mailto:ALAC-Announce@atlarge-lists.icann.org">ALAC-Announce@atlarge-lists.<wbr>icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-announce" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>announce</a><br>
<br>
At-Large Official Site: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">
http://www.atlarge.icann.org</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div style="text-align:center">
<div style="text-align:left">Evan Leibovitch</div>
<div style="text-align:left">Toronto, Canada</div>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px">
<div style="text-align:center">
<div style="text-align:left">Em: evan at telly dot org</div>
</div>
<div style="text-align:center">
<div style="text-align:left">Sk: evanleibovitch</div>
</div>
<div style="text-align:center">
<div style="text-align:left">Tw: el56</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>