<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"><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">
<p>> <br>
> The numbers people also want a separable, contractual relationship. Tell me why names is different.<br>
><span style="color:#1F497D"><o:p></o:p></span></p>
<p>I believe you know the major difference between numbers and names which is the policy source; ICANN is the policy source for names while it is not for numbers.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Not quite correct, Seun.
<o:p></o:p></span></p>
<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: why shouldn’t names have the same structural separation
between the policy maker and the IANA implementer? And if it does, why can’t the policy maker choose the IANA operator?
<o:p></o:p></span></p>
<p>One may argue that it will be in the interest of names(especially the Gs) that ICANN continue to stand.<br>
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">The same can be said for names and is being said for names. Seun, let me make something clear to you and all other ALAC people who have tried to stop separability (interesting
to know why but that is another issue). <o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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. In this latest proposal the community has come to an agreement on a middle ground in which there is separation but in the form of an ICANN affiliate. If you continue
to oppose that you might very well kill the transition, because refusal to accept the latest plan will basically push us back to square one on the internal-external debate. Think carefully about whether that is what you want.
<o:p></o:p></span></p>
</div>
</div>
</body>
</html>