<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1363048857;
mso-list-type:hybrid;
mso-list-template-ids:-2041557544 -1078572110 1351154970 2012494900 -508367276 -1783619244 -315466054 -1964469944 463474070 -2003552220;}
@list l0:level1
{mso-level-start-at:2;
mso-level-number-format:alpha-upper;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:2080978932;
mso-list-template-ids:-1965404556;}
@list l2
{mso-list-id:2093699178;
mso-list-template-ids:1931641214;}
@list l2:level1 lfo2
{mso-level-start-at:0;
mso-level-number-format:alpha-upper;
mso-level-numbering:continue;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear IRT members, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In drafting the text for the Predictability framework, we would you to confirm
</span><span style="color:black">our understanding of Annex E and our approach to implementing the categories of operational and policy issues</span><span style="color:black">
<span lang="EN-US">– per our questions contained in the text below. Please note, we also
<a href="https://docs.google.com/document/d/1Wuq5GgdaeM5pyIpd_I4WEUfUk10NgVEgk1b5P_Ax47U/edit?usp=sharing">
uploaded the question to the IRT’s google drive</a> (with only the comment function enabled).<o:p></o:p></span></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">If you cannot access the document, please contact document:
<a href="mailto:nextround_policyimplementation@icann.org">nextround_policyimplementation@icann.org</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">We are looking forward to hearing back on this issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Lars<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p style="margin:0cm"><span style="color:black">Dear IRT members, </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">In developing the Predictability Framework we would like to propose to make the Framework as efficient and transparent as possible. As a reminder, the intent of the Framework is to ensure that there is transparency
and predictability about any changes that are made to the next round of the New gTLD Program (the Program) after it is launched. To this end, we ask that you confirm our understanding of Annex E and our approach to implementing the categories of operational
and policy issues. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">Annex E of the </span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf"><span style="color:#1155CC">Final Report</span></a><span style="color:black">
provides three categories of operational issues and two categories of policy issues:</span><o:p></o:p></p>
<ol style="margin-top:0cm;padding-inline-start:48px" start="1" type="1">
<li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline">
Minor operational issue<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline">
Non-minor operational issue<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline">
New operational process or significant operational issue<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline">
Changes that may have a policy implication<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline">
New proposals that have have policy implication<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">To make the Framework more transparent and efficient, we propose (A) to combine categories 2 and 3 because regardless of whether an issue is identified as “non-minor” or a “new operational process or significant
operational issue”, ICANN must consult the SPIRT and SPIRT has the option to collaborate with ICANN. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">We also propose (B) to combine categories 4 and 5 because in both categories the Council either determines that policy work is required or that, in fact, the issue requires an operational solution, which would
move it automatically into one of the operational categories. </span><br>
<br>
<o:p></o:p></p>
<p style="margin:0cm;text-indent:0cm;mso-list:l2 level1 lfo2;vertical-align:baseline">
<![if !supportLists]><span style="color:black"><span style="mso-list:Ignore">A.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:black">Rationale for combining categories 2 and 3<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">The main procedural difference between category 1 and categories 2 and 3 is, according to Annex E, that the Standing Predictability Implementation Review Team (SPIRT) has the option to collaborate on solutions
with ICANN org on issues that fall within categories 2 and 3.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">The difference between categories 2 and 3 is that in category 3, the GNSO Council and the ICANN Board can ‘initiate action’.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">It is our understanding that any issue that requires Council action is by definition a policy issue that requires a change to (or new) policy and would thus make it an issue that must fall into the ‘policy’ category.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">The ability of the Board to act is unaffected by the Framework. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">Therefore, we propose to reduce the categories of operational issues to minor and non-minor, with the procedural distinction that the latter gives SPIRT the option to collaborate with ICANN org on the solution.</span><br>
<br>
<o:p></o:p></p>
<ol style="margin-top:0cm" start="2" type="A">
<li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo3;vertical-align:baseline">
Regarding the operational issues:<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">We understand that the Council has only two tools to develop policies: a PDP or an EPDP. With regard to the impact on the Program, whether the GNSO amends existing policy or develops new policy, only a PDP or
EPDP can achieve this. We also note in this context that the Council had previously confirmed to the ODP that policy changes can only affect subsequent rounds, never the current one. </span><o:p></o:p></p>
<p style="margin:0cm"><span style="color:black">If the SPIRT refers an issue to the Council because it or ICANN believes that a policy change may be required, and the Council determines that no policy change is required, then ICANN org will address the issue
via an operational change, in accordance with the Framework. Therefore, we propose to combine categories 4 and 5 into one category of ‘changes that require policy development’. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="color:black">ICANN org believes that this approach is consistent with recommendation 2.1 that “ICANN must establish predictable, transparent, and fair processes and procedures for managing issues that arise in the New gTLD
Program after the Applicant Guidebook is approved which may result in changes to the Program and its supporting processes.” ICANN org has used the predictability framework outlined in Annex E to the Final Report as its guidance in proposing this approach to
implement the framework with the goal of predictability in mitigating issues. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
</div>
</body>
</html>