<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:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@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:TamilMN;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"PMingLiU",serif;
mso-fareast-language:ZH-TW;}
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:"PMingLiU",serif;
mso-fareast-language:ZH-TW;}
span.EmailStyle17
{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:1623733524;
mso-list-type:hybrid;
mso-list-template-ids:-1896423416 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
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="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Kuo-wei:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I am sorry but these responses show an almost Alice in Wonderland-like detachment from what is happening. Your comments fail to address
the very serious concerns raised by the CRISP team, the RIRs and the IETF. My comments below:<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;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-left:4.9pt"><span style="font-family:"TamilMN",serif;color:#1F497D">1.
</span><span style="font-family:"TamilMN",serif">The proposals of IETF and CRISP are in public and delivered to ICG already. They are in ICG's hands now. ICANN (including board) have no intention to intervene the ICG independent process. ICANN staff and Board
continue to support independence of the ICG process.<span style="color:#1F497D"><o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:4.9pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:4.9pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: ICANN has _<i>already</i>_ intervened in the process. It is telling the two communities who have submitted consensus proposals that
it does not accept the proposals. We would appreciate it if you could do something to bridge the obvious gap between what ICANN staff is doing and what the board is saying. </span><br>
<br>
2. The MOU or agreement between ICANN and IETF/NRO exist for many years and continue to exchange the performance information of IANA regularly. ICANN/IANA always do the best to meet the expectation of IETF and NRO, and continue to improve our service. This
is one of key factors for the success operation of global internet. And it proves the current operation is benefit to the communities and global internet users. <span style="color:#1F497D"><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: You are dodging the issue. The issue is not the past agreement between ICANN and NRO, it is the _<i>new</i>_ proposal that the CRISP team has come up with.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:4.9pt"><br>
3. Many on the ICANN Board support the sound engineering principle as recently articulated by Andrew Sullivan, Chair of IAB, that for any working system change it as little as possible, and make gradual reforms over time. The Board continues to encourage
simpler solutions where possible rather than creating new structures that require new legal frameworks and governance models.<span style="color:#1F497D"><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Are you asserting that the proposals of IETF/IANAPLAN and the CRISP team are changing too much? Are you asserting that ICANN staff can, therefore, unilaterally
veto their proposals? We do not see the board “encouraging” simpler solutions through persuasion, we see them attempting to veto solutions. Furthermore, the differences between the existing IETF MoU and supplemental SLA and the new one are tiny, almost unnoticeable.
So even assuming ICANN had the right to override a community consensus to make things “simpler,” ICANN’s actions are not even consistent with this principle.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:4.9pt"><br>
<br>
5. ICANN will support the proposals generated by the community that have reached consensus.<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM: Then ICANN will support the CRISP proposal and the IANAPLAN proposal, and it will cease attempting to undermine or modify them.
<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>