<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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";
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:#330033;}
.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 bgcolor="white" 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">Very good point Avri.<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">Chuck<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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> cwg-rfp3-bounces@icann.org [mailto:cwg-rfp3-bounces@icann.org]
<b>On Behalf Of </b>Avri Doria<br>
<b>Sent:</b> Wednesday, November 05, 2014 6:08 PM<br>
<b>To:</b> cwg-rfp3@icann.org<br>
<b>Subject:</b> Re: [CWG-RFP3] Coordination of Subgroup 3<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
<br>
Perhaps I am being simplistic, but having more information never really hurts, does it?<br>
<br>
If we learn it is as we thought. Great!<br>
If we learn even one wrinkle that or complicating factor we did not know about, all the better?<br>
<br>
avri<o:p></o:p></p>
<div>
<p class="MsoNormal">On 06-Nov-14 05:07, Donna Austin wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Milton<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I agree with you, NTIA would not have announced transition if they had concerns, but I do agree with Kieren that we need to know what NTIA does.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>As a former bureaucrat, I am very conscious that NTIA would most likely have built in layers of administrative processes and guidelines as Kieren suggests in his most recent email. I think it’s important we understand what those are.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Donna<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>[Description: Description: Description: ARI Logo]DONNA AUSTIN<o:p></o:p></pre>
<pre>Policy and Industry Affairs Manager<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>ARI REGISTRY SERVICES<o:p></o:p></pre>
<pre>Melbourne | Los Angeles<o:p></o:p></pre>
<pre>P +1 310 890 9655<o:p></o:p></pre>
<pre>P +61 3 9866 3710<o:p></o:p></pre>
<pre>E <a href="mailto:donna.austin@ariservices.com">donna.austin@ariservices.com</a><a href="mailto:donna.austin@ariservices.com"><mailto:donna.austin@ariservices.com></a><o:p></o:p></pre>
<pre>W <a href="http://www.ariservices.com">www.ariservices.com</a><a href="http://www.ariservices.com/"><http://www.ariservices.com/></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter<a href="https://twitter.com/ARIservices"><https://twitter.com/ARIservices></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>From: Milton L Mueller [<a href="mailto:mueller@syr.edu">mailto:mueller@syr.edu</a>]<o:p></o:p></pre>
<pre>Sent: Wednesday, 5 November 2014 11:51 AM<o:p></o:p></pre>
<pre>To: Donna Austin; 'Kieren McCarthy'; 'Milton Mueller'<o:p></o:p></pre>
<pre>Cc: 'RFP3'<o:p></o:p></pre>
<pre>Subject: RE: [CWG-RFP3] Coordination of Subgroup 3<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Donna:<o:p></o:p></pre>
<pre>Asking NTIA what it does is one thing. (Anyone who wants to can do that.)<o:p></o:p></pre>
<pre>Asking NTIA “if it would have any concerns” about any particular transition proposal, which Kieren also proposed, is not something we should do. It betrays a complete misunderstanding of the nature of this process, imho.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--MM<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>From: <a href="mailto:cwg-rfp3-bounces@icann.org">cwg-rfp3-bounces@icann.org</a><a href="mailto:cwg-rfp3-bounces@icann.org"><mailto:cwg-rfp3-bounces@icann.org></a> [<a href="mailto:cwg-rfp3-bounces@icann.org">mailto:cwg-rfp3-bounces@icann.org</a>] On Behalf Of Donna Austin<o:p></o:p></pre>
<pre>Sent: Wednesday, November 5, 2014 2:38 PM<o:p></o:p></pre>
<pre>To: Kieren McCarthy; Milton Mueller<o:p></o:p></pre>
<pre>Cc: RFP3<o:p></o:p></pre>
<pre>Subject: Re: [CWG-RFP3] Coordination of Subgroup 3<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I think there is value in understanding what NTIA does, and having them inform us of the those details would have value. I appreciate David Conrad’s expertise in this area, but from an administrative and potentially replicative perspective, I support Kieren’s suggestion that we ask “NTIA what it does”.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Donna<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>[Description: Description: Description: ARI Logo]DONNA AUSTIN<o:p></o:p></pre>
<pre>Policy and Industry Affairs Manager<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>ARI REGISTRY SERVICES<o:p></o:p></pre>
<pre>Melbourne | Los Angeles<o:p></o:p></pre>
<pre>P +1 310 890 9655<o:p></o:p></pre>
<pre>P +61 3 9866 3710<o:p></o:p></pre>
<pre>E <a href="mailto:donna.austin@ariservices.com">donna.austin@ariservices.com</a><a href="mailto:donna.austin@ariservices.com"><mailto:donna.austin@ariservices.com></a><o:p></o:p></pre>
<pre>W <a href="http://www.ariservices.com">www.ariservices.com</a><a href="http://www.ariservices.com/"><http://www.ariservices.com/></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter<a href="https://twitter.com/ARIservices"><https://twitter.com/ARIservices></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>From: <a href="mailto:cwg-rfp3-bounces@icann.org">cwg-rfp3-bounces@icann.org</a><a href="mailto:cwg-rfp3-bounces@icann.org"><mailto:cwg-rfp3-bounces@icann.org></a> [<a href="mailto:cwg-rfp3-bounces@icann.org">mailto:cwg-rfp3-bounces@icann.org</a>] On Behalf Of Kieren McCarthy<o:p></o:p></pre>
<pre>Sent: Wednesday, 5 November 2014 9:18 AM<o:p></o:p></pre>
<pre>To: Milton Mueller<o:p></o:p></pre>
<pre>Cc: RFP3<o:p></o:p></pre>
<pre>Subject: Re: [CWG-RFP3] Coordination of Subgroup 3<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>So it strikes me that the obvious question is: let's ask the NTIA what it does and ask it if it would have any concerns if the role simply disappeared.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Kieren<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Tue, Nov 4, 2014 at 2:14 PM, Milton Mueller <<a href="mailto:mueller.syr.edu@gmail.com">mueller.syr.edu@gmail.com</a><a href="mailto:mueller.syr.edu@gmail.com"><mailto:mueller.syr.edu@gmail.com></a>> wrote:<o:p></o:p></pre>
<pre>I agree with David Conrad here. There is no need for the authorizer step.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Milton L Mueller<o:p></o:p></pre>
<pre>Professor, Syracuse School of Information Studies<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Nov 4, 2014, at 13:05, David Conrad <<a href="mailto:david.conrad@icann.org">david.conrad@icann.org</a><a href="mailto:david.conrad@icann.org"><mailto:david.conrad@icann.org></a>> wrote:<o:p></o:p></pre>
<pre>Robert,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Nov 4, 2014, at 3:33 AM, Robert Guerra <<a href="mailto:rguerra@privaterra.org">rguerra@privaterra.org</a><a href="mailto:rguerra@privaterra.org"><mailto:rguerra@privaterra.org></a>> wrote:<o:p></o:p></pre>
<pre>- RZF need to be reviewed for technical accuracy<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>For clarification, currently, the IANA Function Operator (IFO) does not have access to the Root Zone File. The Root Zone File is generated by Verisign prior to signing and distributing to the Root Server Operators (I believe -- I do not know the actual processes used by Verisign for sure, but I can make some educated guesses).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What the IFO does does see is the specific change request prior to it being submitted to NTIA for authorization. There are a number of technical checks performed by the IFO prior to allowing that change request to proceed. I believe those technical checks are documented at <a href="https://www.iana.org/help/nameserver-requirements">https://www.iana.org/help/nameserver-requirements</a> (more generally, <a href="https://www.iana.org/domains/root/help">https://www.iana.org/domains/root/help</a> might be a useful resource).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In the past Verisign also performed a set of technical checks (not exactly sure what they were). I suspect, but do not know for certain, they continue to do those checks.<o:p></o:p></pre>
<pre>- An authorizer process step exists now . In a post NTIA solution, something similar is needed. There is a need to evaluate if a single or multiple authorizers are needed as well as cost that might entail.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Speaking entirely personally, it isn't clear to me that an authorizer step is actually necessary since in practice, by the time the request gets to the authorizer, the affected parties are aware of the change and they'd have raised concerns if they had any. However whether an authorizer step is needed is, of course, for the community to decide.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Regards,<o:p></o:p></pre>
<pre>-drc<o:p></o:p></pre>
<pre>(ICANN CTO, but speaking for myself only. Really.)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Cwg-rfp3 mailing list<o:p></o:p></pre>
<pre><a href="mailto:Cwg-rfp3@icann.org">Cwg-rfp3@icann.org</a><a href="mailto:Cwg-rfp3@icann.org"><mailto:Cwg-rfp3@icann.org></a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-rfp3">https://mm.icann.org/mailman/listinfo/cwg-rfp3</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Cwg-rfp3 mailing list<o:p></o:p></pre>
<pre><a href="mailto:Cwg-rfp3@icann.org">Cwg-rfp3@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-rfp3">https://mm.icann.org/mailman/listinfo/cwg-rfp3</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>