<html 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:0 0 0 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Verisign has a long track record of working with trusted researchers, universities, and an array of partners to publish a significant amount of research and peer-reviewed work on the topic of name collisions, sharing insights from our unique
observation space as a root server operator – see [1] for some examples. We’ve also invested extensively to collect and perform longitudinal analysis on various aspects of this data and make the findings available to the community for consideration, as illustrated
in the long list of citations available at [1] on name collisions, as well as other more recent topics (e.g., to inform KSK roll planning [2]). If you have technical concerns with that work, we welcome your feedback.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As Duane noted, we do NOT monetize root server data.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Conflating those things with the RZM function is not helpful in this context, and to the extent you want to access RZM-related data, ICANN / PTI has it and is very transparent with it already, IMO.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You’re certainly entitled to your opinion about the results of the studies we’ve worked on, but your comments about the motivation behind those studies are wrong, unsupported by facts, and frankly out of bounds. We won’t have anything
else to say on this matter. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Matt Thomas<o:p></o:p></p>
<p class="MsoNormal">Verisign<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[1] https://mm.icann.org/pipermail/ncap-discuss/2019-April/000008.html<o:p></o:p></p>
<p class="MsoNormal">[2] http://www.circleid.com/posts/20191126_recognizing_lessons_learned_from_the_first_dnssec_key_rollover/<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">dns-operations <dns-operations-bounces@dns-oarc.net> on behalf of Rubens Kuhl <rubensk@nic.br><br>
<b>Date: </b>Friday, November 29, 2019 at 8:38 PM<br>
<b>To: </b>"dns-operations@lists.dns-oarc.net" <dns-operations@lists.dns-oarc.net><br>
<b>Subject: </b>[EXTERNAL] Re: [dns-operations] root? we don't need no stinkin' root!<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>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica"><br>
The data could have monetary value. Passwords that are otherwise<br>
difficult to come by might be leaking.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica"><br>
Hi Florian,<br>
<br>
I can assure you that Verisign does not monetize the root server data. If<br>
any other operators do, I'm not aware of it.<br>
<br>
We do utilize root server data for research purposes from time-to-time.<br>
Recent examples include the KSK rollover and name collisions. Less recent<br>
examples include understanding TTL/caching behavior and preparing for the<br>
root ZSK size increase. When DDoS attacks happen, we often analyze the<br>
data to see if we can understand how and why it happened, and to be better<br>
prepared for the next one.</span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Note that the two paragraphs above contradict each other. The current RZM is known to use root server data as anti-competitive measures against new TLD operators with the label of name collision studies, including making studies that other
parties can't reproduce due to being limited to DITL data. <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>
</body>
</html>