<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Hey Bart thanks for this will review this evening <br>
<br>
<div id="AppleMailSignature" dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
On 11 Jan 2019, at 12:24, Bart Boswinkel <<a href="mailto:bart.boswinkel@icann.org">bart.boswinkel@icann.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
.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;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt">Dear James, All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">One of the action items from last meeting was to list the arguments to a limited update of the Remedial Action Procedures. For your convenience I have included the proposed amended RAP in redline and clean
version again.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">As you may recall the amended charter, which is now effective, suggests that the Remedial Action Procedures (RAP) need to be updated. Earlier, 3 changes were proposed (see email from Allan MacGillivray
dated 4 October 2018). These changes are:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">1. Inclusion of a change mechanism<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">2. Ensure in RAP that if CSC determines a performance issue exists, it will inform the ccNSO and GNSO and will be keep the informed. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">3.. Ensure in RAP that if new IFO should be appointed, the new operator would be required to agree to the existing RAP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">In the email dated 11 November 2018, the suggestion was NOT to include the 2<sup>nd</sup> and 3<sup>rd</sup> proposed change.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">As to the 2<sup>nd
</sup> proposed change: the duty of the CSC to inform ccNSO and GNSO of a performance issue is included in the current charter of the CSC where it is stated that "in the event that the CSC invokes the RAP, it will be required to inform the RySG, ccNSO and GNSO
Councils and provide regular status updates". This is a requirement for the CSC and clearly stated in the Charter. Including a similar obligation in the RAP, which are procedures between CSC and PTI (& ICANN Org) may create confusion, in particular if language
is not identical, and unnecessary duplication. There were no comments with respect to this point.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">With respect to the 3<sup>rd</sup> point to ensure that the RAP remain in place post selection new IFO, in the original email it was mentioned that the RAP is a procedure between CSC and PTI (&
ICANN) on how to deal with certain performance issues. Introducing an obligation to ensure adoption by a new IANA Function Operator is well beyond the limited scope of the Remedial Action Procedures and limited role of the CSC. It is strongly advised not to
include it. If it ever comes to a situation that a new IFO needs to be appointed, the requirement that the RAP should remain in place should be dealt with through the new contract between parties, and the appropriate consultation mechanisms. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">In James’ email of 12 November 2018, James stated that he
</span><i><span style="font-size:14.0pt">believe(s) that this is a misunderstanding, the function of the CSC is to oversee on behalf of the customers of the IANA functions, the IANA functions operator (See paragraph 130 of the final CWG-Stewardship) this is
currently PTI and ICANN but the CSC is within its remit as defined in the CWG stewardship proposal to state that we will to the RAP to remain in place for future IFOs (Which of course we all hope will never happen). As defined in paragraph 131 the CSC does
not have a mandate to inmate a chance in the IFO (We have another process for that) but in paragraphs 139-141 at no point is the distinction below mentioned and from my recollection was ever intended.</span></i><span style="font-size:14.0pt">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">To be clear the role oversee on behalf of the customers is NOT a stake, nor is at stake that the RAP should remain in place: this is explicitly included in the current charter (section Scope of
responsibilities, 7<sup>th</sup> paragraph) </span><i><span style="font-size:15.0pt">Should a new IANA Functions Operator be appointed, for example through the recommendations from the Special IANA Naming Function Review Team</span></i><i><span style="font-size:10.0pt">1</span></i><i><span style="font-size:15.0pt">,
the ccNSO and GNSO Councils will require the CSC to review and revise the RAP as necessary with the new operator.</span></i><span style="font-size:15.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt">In addition, the CSC Charter review team noted the following:
</span><i><span style="font-size:13.5pt;font-family:"Arial",sans-serif">The RT remains of the view that there should be a requirement to agree a new RAP with any new IANA Functions Operator and that this should be specified at the time of appointing a new
operator, for example through the recommendations from the Special IANA Naming Function Review Team</span></i><i><span style="font-size:8.5pt;font-family:"Arial",sans-serif">3</span></i><i><span style="font-size:13.5pt;font-family:"Arial",sans-serif">, and
could be ensured by the ccNSO and GNSO Councils when appropriate. </span></i><i><span style="font-size:15.0pt"><o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt"></span><span style="font-size:14.0pt;color:black">Including in the RAP -as suggested – that if new IFO should be appointed, the new operator would be required to agree to the existing RAP, which are procedures
between CSC and PTI (& ICANN Org), may create confusion, and unnecessary duplication.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Bart <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><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">ICANN-CSC <<a href="mailto:icann-csc-bounces@icann.org">icann-csc-bounces@icann.org</a>> on behalf of Bart Boswinkel <<a href="mailto:bart.boswinkel@icann.org">bart.boswinkel@icann.org</a>><br>
<b>Date: </b>Wednesday, 14 November 2018 at 09:42<br>
<b>To: </b>James Gannon <<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>><br>
<b>Cc: </b>"<a href="mailto:ICANN-CSC@icann.org">ICANN-CSC@icann.org</a>" <<a href="mailto:ICANN-CSC@icann.org">ICANN-CSC@icann.org</a>>, Samantha Eisner <<a href="mailto:Samantha.Eisner@icann.org">Samantha.Eisner@icann.org</a>><br>
<b>Subject: </b>Re: [ICANN-CSC] [Ext] Revisions to RAPs Flowing from CSC Charter Review<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">James,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt">The power for the CSC to keep the RAP is not under discussion, it flows from the CWG-Stewardship and was reconfirmed through the CSC Charter review and is included in the current Charter. The question is whether
the RAP should include such a mechanism as well. The RAP is about the remedial action process between the CSC, PTI (& ICANN).
</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Kind regards,</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Bart</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </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">James Gannon <<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>><br>
<b>Date: </b>Monday 12 November 2018 at 22:46<br>
<b>To: </b>Bart Boswinkel <<a href="mailto:bart.boswinkel@icann.org">bart.boswinkel@icann.org</a>><br>
<b>Cc: </b>Allan MacGillivray <<a href="mailto:allan.macgillivray@cira.ca">allan.macgillivray@cira.ca</a>>, "<a href="mailto:ICANN-CSC@icann.org">ICANN-CSC@icann.org</a>" <<a href="mailto:ICANN-CSC@icann.org">ICANN-CSC@icann.org</a>>, Samantha Eisner <<a href="mailto:Samantha.Eisner@icann.org">Samantha.Eisner@icann.org</a>><br>
<b>Subject: </b>Re: [ICANN-CSC] [Ext] Revisions to RAPs Flowing from CSC Charter Review</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">I believe that this is a misunderstanding, the function of the CSC is to oversee on behalf of the customers of the IANA functions, the IANA functions operator (See paragraph 130 of the final CWG-Stewardship) this is currently PTI and ICANN
but the CSC is within its remit as defined in the CWG stewardship proposal to state that we will to the RAP to remain in place for future IFOs (Which of course we all hope will never happen). As defined in paragraph 131 the CSC does not have a mandate to inmate
a chance in the IFO (We have another process for that) but in paragraphs 139-141 at no point is the distinction below mentioned and from my recollection was ever intended.
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I would personally object to the proposal not to include this requirement in the RAPs.</p>
<div>
<p class="MsoNormal"><br>
<br>
<br>
</p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 12 Nov 2018, at 21:26, Bart Boswinkel <<a href="mailto:bart.boswinkel@icann.org">bart.boswinkel@icann.org</a>> wrote:</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica">As to ensuring the RAP remain in place post selection new IFO: The RAP is a procudure between CSC and PTI (& ICANN) on how to deal with cetain performance issues. Introducing an obligation
to ensure adoption by a new IANA Function Operator is well beyond the limited scope of the Remedial Action Procedures and limited role of the CSC, and should therefore not be included. It is suggested that If it ever comes to a situation that a new IFO needs
to be appointed, the requirement that the RAP should remain in place should be dealt with through the new contract between parties, and the appropriate consultation mechanisms.<span class="apple-converted-space"> </span></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><draft RAP revisions November 2018 clean.pdf></div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><draft RAP revisions November 2018 clean.docx></div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><draft RAP revisions November 2018 redline.docx></div>
</blockquote>
</body>
</html>