<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=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 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;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:2056394479;
mso-list-type:hybrid;
mso-list-template-ids:-2141936186 -677725346 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Kavouss,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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"><o:p> </o:p></p>
<p class="MsoNormal">The NTIA has a number of roles – identified in the document which went to consultation in December. I’m sorry if I did not make clear that I was looking at NTIA’s role in letting the contract and its ability to terminate and re-tender.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One key part of the CWG’s discussion has been focussed on separability – 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"><o:p> </o:p></p>
<p class="MsoNormal">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 – where PTI is the contractor currently providing the IANA functions operator, the IANA division
in ICANN. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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"><o:p> </o:p></p>
<p class="MsoNormal">For other roles of the NTIA, we recommend:<o:p></o:p></p>
<p class="MsoNormal">• Discontinuing the third party authorisation of changes to the registries;<o:p></o:p></p>
<p class="MsoNormal">• Further work on dealing with appeals on changes to the registries;<o:p></o:p></p>
<p class="MsoNormal">• 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">• 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">(I might have missed something, so do not treat this as a definitive list. There’s also a lot of detail I have not covered.)<o:p></o:p></p>
<p class="MsoNormal">However, all of these would come back to ICANN to implement or cause to be implemented.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hope this helps<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Martin<o:p></o:p></p>
</div>
</body>
</html>