<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:"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;}
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;}
--></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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">NTIA has not put the Verisign Cooperative Agreement within the remit of the transition process. We have “not examined
it in detail” (as James puts it) because it is not under our control. Sometimes that has been a bit weird, but Drafting Team F, which I participated in, handled this as best we could. Here is the most relevant recommendation, which appears in
</span></font>III.A.iii.a <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">(p.
29) of the proposal</span></font></span></font><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">“Currently updating the Root Zone requires the active participation of three parties, the IFO, the Root Zone Maintainer
and the NTIA. The IFO receives change requests from various sources, validates them, and sends them to the Root Zone Maintainer who, once they are authorized by the NTIA, updates the Root Zone File, DNSSEC signs it, and distributes it to the Root operators.<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">Post transition there will only be the IFO and the Root Zone Maintainer. The CWG-Stewardship is not recommending
any change in the separation between the two at this time. The CWGStewardship is recommending that should there be a proposal to combine the two or make other changes in their respective roles in root zone modification, that it be subject to wide community
consultation”<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" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> NCSG-Discuss
[mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU] <b><span style="font-weight:bold">On Behalf Of
</span></b>James Gannon<br>
<b><span style="font-weight:bold">Sent:</span></b> Tuesday, April 28, 2015 8:53 AM<br>
<b><span style="font-weight:bold">To:</span></b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [NCSG-Discuss] Public Comments on IANA proposal<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<div>
<div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">For the moment the Verisign component has not been examined in detail.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Its expected that there will be no change in that at this time.<o:p></o:p></span></font></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><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="3" color="black" face="Calibri"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;font-weight:bold">From:
</span></font></b><font color="black" face="Calibri"><span style="font-family:"Calibri",sans-serif;color:black">David Post<br>
<b><span style="font-weight:bold">Reply-To: </span></b>David Post<br>
<b><span style="font-weight:bold">Date: </span></b>Tuesday 28 April 2015 13:47<br>
<b><span style="font-weight:bold">To: </span></b>"</span></font><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"><font face="Calibri"><span style="font-family:"Calibri",sans-serif">NCSG-DISCUSS@LISTSERV.SYR.EDU</span></font></a><font color="black" face="Calibri"><span style="font-family:"Calibri",sans-serif;color:black">"<br>
<b><span style="font-weight:bold">Subject: </span></b>Re: Public Comments on IANA proposal<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">At 10:38 AM 4/26/2015, Seun Ojedeji wrote:<br>
<br>
<o:p></o:p></span></font></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">[SNIP] SO:<br>
In the current configuration, PTI is not in the position to issue RFP, it's rather the parent (ICANN) that is in the position to issue RFP based on the recommendation of IRF team/possible escalation from CSC. The later which is not yet very clear. So PTI is
basically entering the current shoes of ICANN and ICANN will be entering the shoes of NTIA post-transition<o:p></o:p></span></font></p>
</blockquote>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
And this may be a dumb question, but just to clarify ... if ICANN enters the shoes of NTIA (the current contract "Administrator"), and PTI enters the shoes of ICANN (the current "IANA Functions Operator"), I assume there will also be someone stepping into the
shoes of VeriSign (the "Maintainer") that will have a contract with both ICANN and PTI - is that corect?<br>
<br>
David<br>
<br>
<br>
<br>
<br>
<br>
*******************************<br>
David G Post - Senior Fellow, Open Technology Institute/New America Foundation<br>
blog (Volokh Conspiracy) </span></font><a href="http://www.washingtonpost.com/people/david-post"><font size="2" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://www.washingtonpost.com/people/david-post<br>
</span></font></a><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">book (Jefferson's Moose)
</span></font><a href="http://tinyurl.com/c327w2n%A0%A0%A0%A0%A0%A0%A0"><font size="2" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://tinyurl.com/c327w2n
</span></font></a><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
music </span></font><a href="http://tinyurl.com/davidpostmusic%A0"><font size="2" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://tinyurl.com/davidpostmusic
</span></font></a><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">publications etc.
</span></font><a href="http://www.davidpost.com /"><font size="2" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://www.davidpost.com
</span></font></a><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
******************************* <o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</body>
</html>