<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 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* 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.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";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle18
{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";}
.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">Thanks Rubens. Who are these consultants who compiled the final report on Root Zone Stability in relation to scaling (i.e. growth in TLDs)?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">NLnet Labs, SIDN LABS, and TNO? Were they hired by the Board or by PTI?<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">What is the degree of participation by PTI in oversight of the stability of the root? Is there an ongoing operational responsibility that rests with PTI to
monitor this as TLDs are added?<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">What is the impact of the statement in the report that “boundless” new gTLDs could affect root stability? Should this affect the WG’s discussions regarding
a period of open applications (first-come first served) AFTER a period of window(s) to deal with pent –up demand?<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">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Anne<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>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#AF272F">Anne E. Aikman-Scalese</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Of Counsel</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">520.629.4428 office</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">520.879.4725 fax</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="mailto:AAikman@lrrc.com" target="_new" title="Email User"><span style="color:#323232">AAikman@lrrc.com</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">_____________________________</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><img border="0" width="115" height="46" id="Picture_x0020_1" src="cid:image004.png@01D2E903.781791F0"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Lewis Roca Rothgerber Christie LLP</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">One South Church Avenue, Suite 700</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Tucson, Arizona 85701-1611</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="http://lrrc.com/" target="_new" title="Lewis Roca Rothgerber Christie Webpage"><span style="color:#323232">lrrc.com</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
</div>
<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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-newgtld-wg-wt4-bounces@icann.org [mailto:gnso-newgtld-wg-wt4-bounces@icann.org]
<b>On Behalf Of </b>Rubens Kuhl<br>
<b>Sent:</b> Saturday, June 17, 2017 7:41 PM<br>
<b>To:</b> gnso-newgtld-wg-wt4@icann.org<br>
<b>Subject:</b> [Gnso-newgtld-wg-wt4] Root Zone Scaling Myths<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">While most current root zone scaling information is available in the CDAR report (<a href="https://www.icann.org/en/system/files/files/cdar-root-stability-final-08mar17-en.pdf">https://www.icann.org/en/system/files/files/cdar-root-stability-final-08mar17-en.pdf</a>), I
did some research regarding root zone scaling, and found that the most comprehensive source to understand is this ICANN report of 2012:<br>
<a href="http://newgtlds.icann.org/en/about/historical-documentation/root-scaling-27jun12-en.pdf">http://newgtlds.icann.org/en/about/historical-documentation/root-scaling-27jun12-en.pdf</a><br>
<br>
Besides all its interesting content, they compiled a list of previous root zone scaling studies that I reproduce here, changing only the link style and updating the links to their current publishing points:<br>
<br>
<br>
<img border="0" width="144" height="1" id="_x0035_96710D7-7AE8-4497-9AC2-FCB16A7E2335" src="cid:image003.png@01D2E903.6E4205C0" alt="page19image2376"><o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
"Appendix A — Previous Studies and Analyses<br>
<br>
A number of studies and analyses have been compiled on the topic of scaling of the DNS Root Zone in the last three years:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span class="apple-tab-span">
</span>• Root Zone Augmentation and Impact Analysis(<a href="https://www.icann.org/en/system/files/files/root-zone-augementation-analysis-17sep09-en.pdf">https://www.icann.org/en/system/files/files/root-zone-augementation-analysis-17sep09-en.pdf</a>) — This
study, also known as the “L-Root Study,” examined the impacts of multifaceted growth of the size of the Root Zone on the performance of “l.root-servers.net,” the root server that is managed by ICANN. This analysis considered the implications of IPv6 addresses,
DNSSEC, as well as new TLDs in a laboratory simulation. The work was conducted by the independent DNS Operations and Research Center (DNS-OARC). This study was published in September 2009, and its conclusions include that root zone servers’ requirements for
memory grow linearly with the number of top-level domains, that the then-deployed software was capable of handling at least 100,000 top-level domains before there was potential degradation in response times. Other software in use had higher thresholds (i.e.
over a million TLDs) before the size of the root zone became a factor.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span class="apple-tab-span">
</span>• Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone(<a href="https://www.icann.org/en/system/files/files/root-scaling-study-report-31aug09-en.pdf">https://www.icann.org/en/system/files/files/root-scaling-study-report-31aug09-en.pdf</a>) —
This report was developed by a specially convened “Root Server Scaling Team” (RSST), comprised of experts from the RSSAC, SSAC as well as experts from outside the ICANN community.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span class="apple-tab-span">
</span>• Summary of the Impact of Root Zone Scaling(<a href="https://archive.icann.org/en/topics/new-gtlds/summary-of-impact-root-zone-scaling-06oct10-en.pdf">https://archive.icann.org/en/topics/new-gtlds/summary-of-impact-root-zone-scaling-06oct10-en.pdf</a>) —
An analysis of issues relating to the impact of Root Zone Scaling was prepared by ICANN and published the document in October 2010. This document considers the findings of the DNS-OARC and RSST reports, and the various root scaling events to date. It identifies
the impacts from IPv6 deployment, TLD growth, DNSSEC deployment and other factors, and concludes the maximum growth to the Root Zone caused by the New gTLD Program is unlikely to cause any disruption.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span class="apple-tab-span">
</span>• Report of the Security and Stability Advisory Committee on Root Scaling(<a href="https://www.icann.org/en/system/files/files/sac-046-en.pdf">https://www.icann.org/en/system/files/files/sac-046-en.pdf</a>) — ICANN’s Security and Stability Advisory Committee
reviewed the original research questions relating to Root Zone Scaling, and provided recommendations relating to processes to handle the increase in the number of top-level domains.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span class="apple-tab-span">
</span>• Explanatory memorandum on Root Zone Scaling(<a href="https://archive.icann.org/en/topics/new-gtlds/root-zone-scaling-15apr11-en.pdf">https://archive.icann.org/en/topics/new-gtlds/root-zone-scaling-15apr11-en.pdf</a>) — As part of a number of briefing
papers associated with the New gTLD Program following dialogue between the ICANN Board and the Governmental Advisory Committee, ICANN published a memorandum concerning Root Scaling in April 2011. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>• Board response to the GAC on Root Zone Scaling(<a href="https://archive.icann.org/en/topics/new-gtlds/root-scaling-30may11-en.pdf">https://archive.icann.org/en/topics/new-gtlds/root-scaling-30may11-en.pdf</a>) —
ICANN published an additional response to the issues raised on dialogue between the ICANN Board and the Governmental Advisory Committee, by providing further detail on how ICANN undertakes to address the ICANN community’s and the GAC’s concerns regarding root
scaling. This response was published in May 2011."<br>
<br>
<img border="0" width="144" height="1" id="_x0000_i1026" src="cid:image003.png@01D2E903.6E4205C0" alt="page19image2376"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Besides those documents, the other interesting documents on this are:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Anticipated delegation rate model: <a href="http://www.icann.org/en/topics/new-gtlds/anticipated-delegation-rate-model-25feb10-en.pdf">http://www.icann.org/en/topics/new-gtlds/anticipated-delegation-rate-model-25feb10-en.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">2010 RSSAC e-mail to Board regarding scaling: <a href="https://www.icann.org/en/system/files/files/murai-to-board-25nov10-en.pdf">https://www.icann.org/en/system/files/files/murai-to-board-25nov10-en.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">SAC 042 (<a href="https://www.icann.org/en/system/files/files/sac-042-en.pdf">https://www.icann.org/en/system/files/files/sac-042-en.pdf</a>) (later superseded by SAC 046)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In short, the anticipated delegation rate model estimated the maximum *evaluation* throughput to be near a 1000 per year, and other ACs responded that it wouldn't be a problem to be delegated. They have not said that the system had a 1000/year
limit, a myth that started only when the number of applications (near 2000) exceeded the high estimate of applications (a thousand), that discussion went stray and landed at that being a limit. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Since those studies, processing power, memory sizes, DNS software design and available bandwidth all greatly increased, so even figures that were determined at that point (like the 100,000 TLDs root zone size) are outdated, although still
limited by latency of the global Internet (which is mainly determined by the speed of light in optical fiber). The root zone now features DNSSEC and IPv6 to most TLDs, so something that was an unknown at that time is now a baseline, the root zone management
system has been completely rewritten, and root server monitoring instrumentation greatly improved (see RSSAC 002, <a href="https://www.icann.org/en/system/files/files/rssac-002-measurements-root-06jun16-en.pdf">https://www.icann.org/en/system/files/files/rssac-002-measurements-root-06jun16-en.pdf</a>)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But, we didn't get an RSSAC response to our CC2 question on the CDAR report, nor they mentioned this in their comments to the CDAR report which were mostly clarifying questions. I believe we could ask them to clarify that and clear the
fog in this topic. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Rubens<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</body>
</html>