<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dear Martin</div><div>You did stated that ICANN assumes NTIA stewardship .At the sane time you stated that CSC will perform operational functions of NTIA.</div><div>May you pls explain the repartition tasks of NTIA stewardship between ICANN and CSC i.e. Since operational tasks of NTIAx will be performed by CSC then what will be performed by ICANN and what will remain to be performed by by ,NTIA non transferred </div><div>Regards</div><div>Kavouss<br><br>Sent from my iPhone</div><div><br>On 23 Apr 2015, at 12:51, Martin Boyle <<a href="mailto:Martin.Boyle@nominet.org.uk">Martin.Boyle@nominet.org.uk</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (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;}
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Kavouss,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As in my earlier mail to the list today, the draft for comments has been published so it is out of our hands to make wording changes now \u2013 we need a stable
document for consultation to be fair to everyone now working on their analysis and comments. However, I think that section III.A, The elements of this proposal, on pp 18 onwards has to be seen in its entirety as it goes over the different elements of the
model and the relationship between them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I perhaps should have mentioned yesterday that the names of the different elements have changed in drafts from those given in the chart I used to talk us through
the document. In the consultation draft, \u201cperiodic review function\u201d or PRF on the chart became the \u201cIANA function review\u201d or IFR: while the proposal is for the reviews to take place every five years, it is possible for a special review to be set up, so the
term periodic does not quite match with the proposal. Otherwise I think I did manage to keep to current terminology.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Martin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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 lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kavouss Arasteh [<a href="mailto:kavouss.arasteh@gmail.com">mailto:kavouss.arasteh@gmail.com</a>]
<br>
<b>Sent:</b> 22 April 2015 19:02<br>
<b>To:</b> Martin Boyle<br>
<b>Cc:</b> <a href="mailto:internal-cg@ianacg.org">internal-cg@ianacg.org</a><br>
<b>Subject:</b> Re: ICG Call: NTIA Role<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Dear Martin,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Tks for explanation<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The first part of the message " In the model in front of us today, at transition ICANN would take the NTIA responsibility for a contract with its affiliate (subsidiary) the PTI " is not clearly mentioned in CWG where as it was especifically
mentioned in Legal Memo dated 04 April as I did cite in previous message .<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">For the rest I have the same understanding as your<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> Consequently, the part that ICANN WILL PERFORM THE CURRENT ROLE OF NTIA needs to be mentioned at the beginning of the CSC paragraph e.g.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">While ICANN would take the NTIA responsibility for a contract with its affiliate (subsidiary) the PTI \u2013 where PTI is the contractor currently providing the IANA functions operator, the IANA division in ICANNm, CSC is to carry out the operational
responsibilities associated with managing the contract.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This paraphrasing is necessary to avoid misinterpreting the Roles of icann AND THE rOLE of CSC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">It is always good to talk with Professional that nicely, quietly and respectfully provide the clarification.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Aggressive Approach does not work at least with me.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I have never ever yeilded to any pressure at all and will not do it<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Tks again it was a kind and helpful clarification.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kavouss . <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2015-04-22 19:01 GMT+02:00 Martin Boyle <<a href="mailto:Martin.Boyle@nominet.org.uk" target="_blank">Martin.Boyle@nominet.org.uk</a>>:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi Kavouss,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There seems to me that there was some confusion between us on the role of the NTIA and how the names proposal would address this.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The NTIA has a number of roles \u2013 identified in the document which went to consultation in December. I\u2019m sorry if I did not make clear that I was looking at NTIA\u2019s role in letting
the contract and its ability to terminate and re-tender.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">One key part of the CWG\u2019s discussion has been focussed on separability \u2013 a role that NTIA currently has by virtue of its contract with ICANN for the role of IANA functions operator.
The contract approach allows the role to be reassigned in the case of the IANA functions operator failing to meet obligations and failing to remedy the failings.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">In the model in front of us today, at transition ICANN would take the NTIA responsibility for a contract with its affiliate (subsidiary) the PTI \u2013 where PTI is the contractor currently
providing the IANA functions operator, the IANA division in ICANN. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The role of the CSC is to carry out the operational responsibilities associated with managing the contract. Its role is quite limited in that it monitors performance against the
agreed service level targets and works with PTI to ensure that concerns are addressed. The CSC does not make the decision on the future of the contract.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">For other roles of the NTIA, we recommend:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">\u2022 Discontinuing the third party authorisation of changes to the registries;<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">\u2022 Further work on dealing with appeals on changes to the registries;<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">\u2022 Using the CSC and PRF to process changes to service level agreements and other operational conditions; and
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">\u2022 Using the CSC (and/or the PRF) to initiate discussion on structural or operational changes (the introduction of DNSSEC was the example I used) but leave open for the
moment who might authorise change.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(I might have missed something, so do not treat this as a definitive list. There\u2019s also a lot of detail I have not covered.)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">However, all of these would come back to ICANN to implement or cause to be implemented.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hope this helps<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#888888"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#888888">Martin<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div></blockquote></body></html>