<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;
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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{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;}
--></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">Alissa<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I agree that we should try to integrated Paragraph 55 and my proposed text. Also agree with your other proposed edits.
<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">Below, is a first stab at merging the two\u201d<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">===<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">The ICG notes that, under the current IANA Functions Contract, the DNS Root Zone Management process currently has three functional roles: the IANA Functions Operator
(IFO), the Root Zone Maintainer (RZM), and the Root Zone Administrator (RZA). A complete and finalized transition requires revising the relationship between the current IANA functions operator (ICANN), the current RZM (Verisign) and the current Root Zone Administrator
(the U.S. Commerce Department NTIA). Insofar as those revisions require amendments to (or elimination of) the cooperative agreement between the NTIA and Verisign, the process will be controlled by the NTIA, not the ICG. This \u201crelated and parallel transition,\u201d
as the NTIA described it in its March 2014 announcement, involves interactions between NTIA, ICANN and Verisign that are outside of the ICG process. Nevertheless, the NTIA itself has recognized that \u201caspects of the IANA functions contract are inextricably
intertwined with the VeriSign cooperative agreement,\u201d and thus the results of that process must be consistent with the ICG proposal\u2019s approach to the IANA Functions.<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">The CWG Stewardship proposal (paragraph 1150) states that the RZA role need not be continued. However, since the RZA (NTIA) has served as the linkage between
the IFO and the RZM and there is currently no direct agreement between the RZM and the IFO for the Root Zone Management process, the ICG notes that some form of written agreement between the IANA functions operator and RZM that clearly defines the roles and
responsibilities of both parties is essential for the secure, stable and resilient operation of the Root Zone of the DNS when the NTIA withdraws from the Root Zone Management process. [Insert here text about separating the roles or changing roles once a response
received from CWG]<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">So far the NTIA\u2019s process seems to have built upon the output of the CWG-Stewardship proposal. The names CWG proposed elimination of the NTIA\u2019s root zone change
authorization function and described a set of guidelines and principles regarding post-transition root zone administration. To the ICG, the post-transition RZM architecture proposed in an NTIA-solicited document by ICANN and Verisign (cite) seems to be consistent
with those guidelines and principles. <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">In the public comment period, however, a wide range of stakeholders expressed concern about the transparency of the parallel process and the uncertainty created
by its status as a private negotiation among NTIA, Verisign and ICANN. Commenters seemed especially concerned about whether the global multistakeholder community would be consulted about the new arrangements before they are finalized, and whether the changes
might permit significant changes in roles, such as ICANN taking over the RZM function. In response to these concerns, the ICG took the following actions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">\u2022 Asked for clarification from CWG-Stewardship about its policy toward the separation of the IANA Functions Operator, ICANN and the Root Zone Maintainer;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">\u2022 Asked the CWG-Stewardship to confirm that the Verisign/ICANN proposal for revising Root Zone Management post-transition meets their requirements<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">===<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"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<p class="MsoNormal">Thanks Milton. I think this is good. I have some specific comments below. One over-arching question: how do you think this text fits together with the text currently in paragraph 55 of the proposal? Would we keep both, combine them somehow,
or replace paragraph 55 with the text below? I quite like the detail in paragraph 55 and the references to the CWG proposal, so perhaps some version of it could remain by combining it with your second paragraph below and editing the combined paragraph.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Sep 26, 2015, at 8:52 AM, Mueller, Milton L <<a href="mailto:milton.mueller@pubpolicy.gatech.edu">milton.mueller@pubpolicy.gatech.edu</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I thought I had sent this out before but now I am not sure. So to be safe I send it now (again?)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">The ICG recognizes that a complete and finalized transition requires more than implementing its own proposal. It also requires revising the relationship between
the current Root Zone Maintainer (Verisign), Root Zone Administrator (the U.S. Commerce Department) and IANA functions operator (ICANN). Insofar as those revisions require amendments to (or elimination of) the cooperative agreement between the NTIA and Verisign,
the process will be controlled by the NTIA, not the ICG. This \u201crelated and parallel transition,\u201d as the NTIA described it in its March 2014 announcement, involves interactions between NTIA, ICANN and Verisign that are outside of the ICG process. Nevertheless,
the NTIA itself has recognized that \u201caspects of the IANA functions contract are inextricably intertwined with the VeriSign cooperative agreement,\u201d and thus the results of that process must be consistent with the ICG proposal\u2019s approach to the IANA Functions.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">So far the NTIA process seems to have built upon the output of the CWG-Stewardship proposal. The names CWG proposed elimination of the NTIA\u2019s root zone change
authorization function and described a set of guidelines and principles regarding post-transition root zone administration. To the ICG, the post-transition RZM architecture proposed in an NTIA-solicited document by ICANN and Verisign does not seem to be inconsistent
with those guidelines and principles.<span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think we should cite the document. Also, I would suggest \u201cseems to be consistent\u201d rather than the double negative.<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">In the public comment period, however, a wide range of stakeholder groups expressed concern about the transparency of the
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would suggest \u201cstakeholders\u201d rather than \u201cstakeholder groups.\u201d<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Alissa<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">parallel process and the uncertainty created by its status as a private negotiation among NTIA, Verisign and ICANN. Commenters seemed especially concerned about
whether the global multistakeholder community would be consulted about the new arrangements before they are finalized, and whether the changes might permit significant changes in roles, such as ICANN taking over the RZM function. In response to these concerns,
the ICG took the following actions:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal" style="text-indent:-.25in;line-height:11.65pt"><span style="font-size:11.0pt;font-family:Symbol">�</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">Asked
for clarification from CWG-Stewardship about its policy toward the separation of the IANA Functions Operator, ICANN and the Root Zone Maintainer;</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:.5in;text-indent:-.25in;line-height:11.65pt">
<span style="font-size:11.0pt;font-family:Symbol">�</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:white">Asked the CWG-Stewardship to confirm
that the Verisign/ICANN proposal for revising Root Zone Management post-transition meets their requirements</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;background:yellow"><Additional text would depend on the result of these inquiries. E.g., if CWG replies to our first question saying, \u201cyes, the second principle implies that different
organizations should be providing IFO and RZM, and before that changes there should be a consultation that obtains consensus\u201d then we can say to the NTIA: \u201cmake sure any revisions in the Verisign cooperative agreement/ICANN arrangements you approve are not
inconsistent with that.\u201d If CWG says that the proposal of ICANN-Verisign meets their requirements then we have no need to make any comment. If it does not we need to convey to NTIA-ICANN-Verisign what is missing. ></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dr. Milton L. Mueller<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Professor, School of Public Policy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Georgia Institute of Technology<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Internal-cg mailing list<br>
</span><a href="mailto:Internal-cg@mm.ianacg.org"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">Internal-cg@mm.ianacg.org</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>