<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 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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;
color:#330033;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:#330033;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:#330033;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{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:70.85pt 70.85pt 70.85pt 70.85pt;}
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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Maarten<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I guess you didn’t understand my point. The possibility of separating the execution of the functions has nothing
to do with how well or how poorly the IANA practical work is performed now. It has to do precisely with what you say needs attention: the oversight function. Oversight for names may or may not be optimized by combining it with oversight for the other functions.
What happens, e.g., if one part is performed well and the other poorly? The requirements and procedures are radically different. This is a fact.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">At any rate, I would encourage you to follow your own advice and “keep busy” developing a proposal that solve the
problem for names, and let the other functions worry about their issues, and let the ICG worry about how they fit together when the proposals are in. Deal?
<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><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 style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" color="black" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;font-weight:bold">From:</span></font></b><font size="2" color="black" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org] <b>
<span style="font-weight:bold">On Behalf Of </span></b>Maarten Botterman GNKS<br>
<b><span style="font-weight:bold">Sent:</span></b> Monday, October 27, 2014 1:11 PM<br>
<b><span style="font-weight:bold">To:</span></b> cwg-stewardship@icann.org<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [CWG-Stewardship] [IANA-issues] CWG RFP 2C - Draft Triage of IANA Functions Contract<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" color="#330033" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’m with Avri on this. Never heard anyone being unhappy about the IANA practical work (“IANA functions”) as such,
I think the world sees that that works, and an old saying in IT is “don’t fix it if it isn’t broken”. It works. Let’s keep the focus on where it is to be, effectively: on the oversight function organization. A challenge big enough to keep us busy without also
considering a different organization of the functions at the same time – in particular when there is no apparent need for that.<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Or did I miss something?<o:p></o:p></span></font></p>
<p class="MsoNormal"><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"><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"><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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" color="black" face="Tahoma"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext;font-weight:bold">From:</span></font></b><font size="2" color="black" face="Tahoma"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext">
<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b><span style="font-weight:bold">On Behalf Of </span></b>Avri Doria<br>
<b><span style="font-weight:bold">Sent:</span></b> maandag 27 oktober 2014 3:20<br>
<b><span style="font-weight:bold">To:</span></b> <a href="mailto:cwg-stewardship@icann.org">
cwg-stewardship@icann.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [CWG-Stewardship] [IANA-issues] CWG RFP 2C - Draft Triage of IANA Functions Contract<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" color="#330033" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="3" color="#330033" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" color="#330033" face="Times New Roman"><span lang="NL" style="font-size:12.0pt">On 27-Oct-14 00:31, Milton L Mueller wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><font size="2" color="#330033" face="Courier New"><span lang="NL" style="font-size:10.0pt">C.2.4. Assumes that all of the IANA functions are in the same entity. This assumption is not warranted at the present time.<o:p></o:p></span></font></pre>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" color="#330033" face="Times New Roman"><span lang="NL" style="font-size:12.0pt"><br>
<br>
Except that the assumption of this exercise is to change as few things as possible and an assumption that they can or even should be moved to seperate entities is not warranted. The solition does not need to match the structure of the operational communities
doing the recommendations.<br>
<br>
Without an anaylisis of the effect of seperation, I think it unwise to assume they can or should be split.<br>
<br>
I therefore would rather assume that the unity of IANA should be preserved until such time as it is proved that sperating them is the better solution. And until it is proven that sperating them invovles no risk. Even the IETF which is assuming it can pull
out of IANA at any time has not done a complete analysis of the risks of doing so. Until we are sure that it does not pose a risk to the Internet, we ought to be careful about dumping this requirement.<br>
<br>
avri<o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>