<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 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Seun:<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">ICANN is BOTH the policy source for names AND the maintainer of the IANA registry for names. So you are ducking the question:</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:#1F497D">SO: </span>No i am not, you asked for differences NOT similarities and just for the record, ICANN is NOT currently IANA maintainer for names, VeriSign is. ICANN is however the IANA manager for both names and
numbers (including being maintainer for numbers)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Sorry, but there is some verbal confusion here. I called ICANN the maintainer of the IANA names registry. That is what ICANN’s IANA does, it edits and updates
the root zone file for DNS. I know that NTIA’s idiosyncratic terminology calls Verisign, which DNSSEC-signs and publishes the root zone maintained by IANA, the “RZ Maintainer.” But that doesn’t change the fact that currently, in the names area, the IANA functions
and the policy development functions are combined in the same entity, ICANN, and in numbers and protocols they are not. My question to you – which you still have not answered – is this:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">why shouldn’t names have the same structural separation between the policy maker and the IANA implementer?
<o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:#1F497D">SO: </span>I am not sure any part of my statement implied what you have stated above.
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Just answer the question. Stop avoiding it. Don’t we need to separate IANA into PTI to get to the same place as numbers and protocols? Do you oppose separability
on principle? Or do you support it now? </span><o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p><span style="color:#1F497D">SO: </span>One may argue that it will be in the interest of names(especially the Gs) that ICANN continue to stand.<span style="color:#1F497D"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: What does “continue to stand” mean? Do you mean have a permanent monopoly on the provision of the names-related IANA functions? Or do you mean something else?<o:p></o:p></span></p>
<p><span style="color:#1F497D">SO: </span>For numbers and protocol it will make a lot of sense to move it's database from ICANN (when required) because it's policy development process is independent of ICANN. Same cannot be said for names(excluding ccTLD) and
maybe that is why some don't see much sense in the proposed contractual arrangements for names.<o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Why does it make sense for numbers and protocols and not for names? You have never answered this.
<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: If you don’t accept legal separation of PTI and continue to push for an ICANN monopoly on IANA, there will be no consensus on this latest proposal and the transition will probably
fail. I can guarantee you that there will never be consensus on a purely internal solution.</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D">SO:
</span>With due respect Milton, I am quite amazed at your statement above as i have not said ALAC is stopping anything. Please remember that i am also a member of the CWG and have been following the process quite keenly (to the best of my ability). The proposal
we currently have was presented to the community on behalf of the entire CWG and its only the community's view that would ultimately determine next steps for the CWG proposal. Neither of us can stop anything if there is consensus from majority of the community
towards a certain solution. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: So you agree that PTI should be formed as a separate legal entity? Will you say this in your public comments or not?
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>