<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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: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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div>
<div>
<div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-left:5.25pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Seun Ojedeji [mailto:seun.ojedeji@gmail.com]
<br>
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Not quite right. ICANN could operate the IANA, as a fully separated subsidiary, if it won the contract from a new contracting authority. The issue is whether it just “gets”
IANA or whether it has to earn it.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Okay thanks for clarifying this and i also share the fact that ICANN has to earn IANA by being accountable to its customers. However you seem to be indicating that the only way to achieve this is by continuing
with the contracting approach which i don't think should be the case. There are 2 major ways by which i think ICANN can be reminded of the fact that it doesn't own the funtions and by so has no absolute control over it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- Through the various policy processes (which i think you also agreed to in your mail)<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Policy processes cannot take IANA away from ICANN nor can they provide appropriate levels of oversight over policy implementation. Indeed, the policy process
is entirely dependent on ICANN to implement it, and if ICANN ignores the PDP and implements what it prefers (which has happened a few times) we have no recourse.
<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>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">The reality is that the functions are actually in effect because many service providers subscribed to it. If ICANN so extremely miss-behaves then it definitely won't be the end of the Internet as i would expect
major service providers to be able to find a way around this. <span style="color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">They would find away around it: by chagning their service provider, i.e. by taking away the contract. I don’t understand why you
resist this simple idea. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hmm....i think i can almost +1'd this but like to get some clarification. Are you saying that there is already an existing separation between names policy and IANA names function? If yes then i agree to that.
Are you also saying that the separation was made possible because of the contract? If Yes, no problem. Would you not also agree then that the current separation can be maintained even without the contract?
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:5.25pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">No, I would not agree with that last part. How can any reasonable person agree with that? If there is no contractual obligation to maintain the separation, then the separation will
collapse as soon as it is in ICANN’s organizational self-interest to do so. <o:p>
</o:p></span></p>
</div>
<div>
<p class="MsoNormal">Okay i will further explain, historically and from my discussion with people who where there when it all started. I have figured that ICANN was purpose built; which is to ultimately coordinate the internet resources and the reason why there
was need for contract is to allow the then young and vulnerable ICANN grow to maturity before it is fully allowed to be independent. So i think going out of this contracting processes should indeed be the next phase in the growing process of ICANN and it absolutely
may not make any much difference if it leaves one contracting regime to enter into another.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When people build things, they can make mistakes. ICANN has inadequate accountability to be given untrammelled control of the DNS root and number spaces.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>