<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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin-top:0in;
        margin-right:0in;
        margin-bottom:6.0pt;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Helvetica","sans-serif";
        color:black;
        mso-fareast-language:EN-CA;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;
        mso-fareast-language:EN-CA;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        color:black;
        mso-fareast-language:EN-CA;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">In fact, my understanding is that the CSC cannot launch a Special IFR but only escalates to the ccNSO and GNSO for that consideration. Donna/Staffan – please correct me if
I am wrong on that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-US">
cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org] <b>
On Behalf Of </b>Jonathan Robinson<br>
<b>Sent:</b> Thursday, June 11, 2015 3:45 AM<br>
<b>To:</b> 'Olivier MJ Crepin-Leblond'; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Triggering of Special IFR<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D">Olivier,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D">I agree with you understanding in the second instance i.e. as per Annex F.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-CA">" </span><span style="color:#3366FF">Following the exhaustion of the above escalation mechanisms, the ccNSO and GNSO will be responsible for checking and reviewing the outcome of the CSC process
(as defined in Annex G), and the IANA Problem Resolution Process (as defined in Annex J) and for determining whether or not a Special IFR is necessary. After consideration, which may include a public comment period and must include meaningful consultation
with other SO/ACs, the Special IFR could be triggered by a supermajority vote of each of the ccNSO and GNSO Councils according to their normal procedures for determining supermajority.
</span>"<br>
<br>
To me, this translates to: a special IFR can be launched by CSC *and* GNSO *and* ccNSO agreeing that a special IFR needs to be launched. It is impossible for the CSC *or* the GNSO *or* the ccNSO to launch a special IFR singlehandedly.<span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-family:"Calibri","sans-serif";color:#1F497D">Jonathan<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB">
Olivier MJ Crepin-Leblond [<a href="mailto:ocl@gih.com">mailto:ocl@gih.com</a>] <br>
<b>Sent:</b> 11 June 2015 08:30<br>
<b>To:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] Triggering of Special IFR<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-CA">Hello all<br>
<br>
looking at the slide deck for the presentation (downloadable from <a href="https://community.icann.org/pages/viewpage.action?pageId=53778352">
https://community.icann.org/pages/viewpage.action?pageId=53778352</a> ), page 12 , I raised a question on the first Webinar.<br>
The slide says: </span><span lang="EN-CA" style="color:#3366FF">"Review cycles: 1st review to occur no more than 2 years post-transition; then every 5 years. Or by special request of CSC, GNSO, or ccNSO (Special IFR)."</span><span lang="EN-CA"><br>
<br>
I took up this sentence and asked: "A Special IFR can be launched by CSC, GNSO, *or* ccNSO? I was under the impression that a Special IFR can be launched by CSC, GNSO *and* ccNSO" only.<br>
<br>
I was told, in response, that the slide is correct, and an IFR can be launched by the CSC, or ccNSO or GNSO.<br>
<br>
The *or* vs. *and* is very important.<br>
<br>
So I looked at the proposal again, Annex F.<br>
<br>
" </span><span style="color:#3366FF">Following the exhaustion of the above escalation mechanisms, the ccNSO and GNSO will be responsible for checking and reviewing the outcome of the CSC process (as defined in Annex G), and the IANA Problem Resolution Process
(as defined in Annex J) and for determining whether or not a Special IFR is necessary. After consideration, which may include a public comment period and must include meaningful consultation with other SO/ACs, the Special IFR could be triggered by a supermajority
vote of each of the ccNSO and GNSO Councils according to their normal procedures for determining supermajority.
</span>"<br>
<br>
To me, this translates to: a special IFR can be launched by CSC *and* GNSO *and* ccNSO agreeing that a special IFR needs to be launched. It is impossible for the CSC *or* the GNSO *or* the ccNSO to launch a special IFR singlehandedly.<br>
<br>
So is the slide on page 12 and the response I was given on the First Webinar right or wrong? This is a serious issue.<br>
<br>
Kind regards,<br>
<br>
Olivier<span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:EN-GB"><o:p></o:p></span></p>
</div>
</body>
</html>