<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<base href="x-msg://68/"><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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:489831701;
mso-list-type:hybrid;
mso-list-template-ids:-1770605302 -1504025922 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:48.75pt;
text-indent:-30.75pt;
color:windowtext;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:.5in;margin-bottom:5.0pt;margin-left:48.75pt;text-indent:-30.75pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><span style="mso-list:Ignore">1.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]>It is important that Post Transition IANA, as a whole, remains anchored with Protocols and Numbering, that is with IETF and the RIRs. There are several reasons for this.
<font color="#1f497d"><span style="color:#1F497D"><o:p></o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.0in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#5b9bd5" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font color="black"><span style="color:windowtext">MM: Then
be advised that both RIRs and IETF consider the IANA functions operator to be a simple clerical service that is provided to them on a contractual basis, and wish to maintain a clear and non-negotiable right to terminate the contract and switch providers.
<o:p></o:p></span></font></span></font></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:.5in;margin-bottom:5.0pt;margin-left:48.75pt;text-indent:-30.75pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><span style="mso-list:Ignore">2.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]>( a ) Open Internet Standards are critical for fair competition and low entry barriers. Governments and Users have an existential interest in the work of IETF. ( b ) Numbering, and particularly communications numbering
are of critical interest to public policy. Most governments have accepted with more-or-less good grace that that shall continue to be done for the Internet by the RIRs. However, I believe that in the last resort their ability to comment and advise on numbering
policy through ICANN/IANA/GAC is a significant element in their acceptance.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Once again you are showing a very fundamental misunderstanding about what IANA functions are and what the IANA functions operator
(IFO) does. Policy is made outside of the IANA functions operator (IFO); IFO merely implements and keeps track of registry entries in a way that maintains global uniqueness. Advising on number policy will be done through the RIRs (not through ICANN, unless
it is a global policy); advising and development of naming policy will be done through ICANN’s GNSO, ccNSO, ALAC and GAC; development of standards and protocols is done by IETF. In all three cases, the IFO merely changes the registries in ways directed by
the three ‘customers’ (ICANN, RIRs, IETF). IFO is irrelevant to the making of policy.
<o:p></o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.0in;margin-bottom:5.0pt;margin-left:48.75pt">
<font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
As a long-time student and practitioner of industrial economics applied to the information society, let me say that IANA, as a fully privatised commercial service, would become financially invaluable to its owners.<font color="#1f497d"><span style="color:#1F497D"><o:p></o:p></span></font></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Another misunderstanding. IANA is a clerical service. If it is properly confined to making the changes in registry entries as directed
by IETF, RIRs and ICANN, it performs a vital but not lucrative service. The numbers top level registry could probably be run for less than $100,000/ year. The labor-intensive protocols registry could probably be done for $1-2 million a year. As long as IFO
is not the root zone maintainer, the names part is not that expensive, either. And if any IFO tries to exploit its role to make it more “financially invaluable,” then the solution is to make it EASY, not hard, to switch service providers.
<o:p></o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.0in;margin-bottom:5.0pt;margin-left:48.75pt">
<font size="3" face="Times New Roman"><span style="font-size:12.0pt">The second line of defence is to make it as difficult as possible to separate IANA from ICANN (as to be reformed under the CCWG Accountability proposals). In the last resort, a 'separate'
IANA must be protected as a public service against any form of capture. However, that last resort is not yet credible. There are no
<font color="#1f497d"><span style="color:#1F497D"><o:p></o:p></span></font></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: The _<i><span style="font-style:italic">best</span></i>_ protection against capture is to make sure that IANA is not a fixed monopoly
in the control of a single player. If it is a monopoly and the operator cannot be changed, then there will be all kinds of incentives to ‘capture’ it and exploit it as for economic or political purposes. <o:p></o:p></span></font></p>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:1.5in;margin-bottom:5.0pt;margin-left:0in">
<font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
</div>
</body>
</html>