<html xmlns:v="urn:schemas-microsoft-com:vml" 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" xmlns:ns0="#unknown">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style id="css_styles">v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:1314524143;
mso-list-template-ids:-210481486;}
@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 l0:level2
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:1435127170;
mso-list-template-ids:1983285490;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thank you for the input, Jeff. I suggest we address the substance of your and any other comments that may come in together during our next call.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">One suggestion that may be helpful not just to staff but also to fellow IRT members: if additional is provided, like Jeff did below, it would be helpful to point to relevant sections
in the <a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf">
Final Report</a>, so that it is clear to everyone whether it is based on a recommendation, an implementation guidance or other relevant text. In Jeff’s case, I assume he is referring to the process description c. on page 319-320 (Annex E) of the Final Report:
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span lang="EN-US">“</span>ICANN org must inform the SPIRT of issues arising in this category and the SPIRT will have the option to collaborate with ICANN org as a solution is developed. The GNSO Council or ICANN Board may also initiate
action on an issue they believe to be in this category and request assistance from the SPIRT. Once changes are agreed, changes should be communicated to all impacted (or</i><i> reasonably foreseeable impacted) parties prior to deployment of the change, and
shall be reported on subsequent to their implementation in a change log, or similar</i><i><span lang="EN-US">.”</span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Lars<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"jeff@jjnsolutions.com" <jeff@jjnsolutions.com><br>
<b>Reply to: </b>"jeff@jjnsolutions.com" <jeff@jjnsolutions.com><br>
<b>Date: </b>Thursday, 22 June 2023 at 22:41<br>
<b>To: </b>Lars Hoffmann <lars.hoffmann@icann.org>, "subpro-irt@icann.org" <subpro-irt@icann.org><br>
<b>Subject: </b>[Ext] Re: [SubPro-IRT] On Predicabilty<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Thanks Lars for these questions. I provide these answers in my own personal capacity based on my in depth understanding about the SubPro Recommendations and PDP.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"> First, I believe we must also consider that changes or new proposals not only impact ICANN Org and the GNSO Council, but rather can potentially have significant impacts on
Applicants and members of the community that participate in the various processes such as commenters, objectors, etc. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">I have no issue with combining numbers 2 and 3 provided that ICANN follows the standard set forth in c, and not the standard set forth in b of Annex E. Though both (b) and
(c) require collaboration with the SPIRT, New Processes and/or significant changes to Internal Processes (c), require
<u>agreement</u> on changes whereas (b) does not require. In other words, if you combine them both into one category, then <u>agreement of the SPIRT to implement any of the changes or new processes will be required.</u> You cant take the lower standard of
only collaboration (in b) and use that as the new standard for (c). That is a material difference.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">I am still looking at the combination of 4 and 5.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Sincerely,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Jeff<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="signature_old">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><img border="0" width="364" height="121" style="width:3.7916in;height:1.2604in" id="_x0000_i1025" src="cid:image001.png@01D9A5D6.8F0FC4E0"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">------ Original Message ------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">From "Lars Hoffmann" <<a href="mailto:lars.hoffmann@icann.org">lars.hoffmann@icann.org</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">To "<a href="mailto:subpro-irt@icann.org">subpro-irt@icann.org</a>" <<a href="mailto:subpro-irt@icann.org">subpro-irt@icann.org</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Date 6/22/2023 7:56:31 AM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Subject [SubPro-IRT] On Predicabilty<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="x1d89301a2bf5480">
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 8.0pt;margin-left:3.75pt;margin-top:2.25pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Dear IRT members, </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">In drafting the text for the Predictability framework, we would you to confirm
</span>our understanding of Annex E and our approach to implementing the categories of operational and policy issues
<span lang="EN-US">– per our questions contained in the text below. Please note, we also
<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1Wuq5GgdaeM5pyIpd_I4WEUfUk10NgVEgk1b5P_Ax47U/edit?usp=sharing__;!!PtGJab4!5kfCSDnuvYlYh3Uqbwj84_4XbMHIOleC5MIJCkNa8uuZ89tKxey5stVc-1Zc0ZhayCH5WRxpFk-00Gzju3_k2stvUmA$">
<span style="color:#0563C1">uploaded the question to the IRT’s google drive [docs.google.com]</span></a> (with only the comment function enabled).</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></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"><span style="color:#0563C1">nextround_policyimplementation@icann.org</span></a>.
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">We are looking forward to hearing back on this issues.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Best wishes,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Lars</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Dear IRT members, <o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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. <o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Annex E of the
<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf__;!!PtGJab4!5kfCSDnuvYlYh3Uqbwj84_4XbMHIOleC5MIJCkNa8uuZ89tKxey5stVc-1Zc0ZhayCH5WRxpFk-00Gzju3_kgWuF0Nk$">
<span style="color:#1155CC">Final Report</span><span style="color:#0563C1"> [gnso.icann.org]</span></a> provides three categories of operational issues and two categories of policy issues:<o:p></o:p></span></p>
<ol style="margin-top:0cm;padding-inline-start:48px" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Minor operational issue<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Non-minor operational issue<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">New operational process or significant operational issue<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">Changes that may have a policy implication<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo1;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">New proposals that have have policy implication<o:p></o:p></span></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.
<o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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. <o:p>
</o:p></span></p>
<p style="margin:0cm;vertical-align:baseline"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">A.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.
<o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">The difference between categories 2 and 3 is that in category 3, the GNSO Council and the ICANN Board can ‘initiate action’.<o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.<o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">The ability of the Board to act is unaffected by the Framework. <o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="2" type="A">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo2;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif"> Regarding the operational issues:<o:p></o:p></span></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.
<o:p></o:p></span></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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’.
<o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif">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.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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"> </span><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>