<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:"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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Jeff,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With item #1 below, I’m going to say we discussed those impacts within the context of name collisions several times. Let me just talk to the first technology change w/r/t Qname Minimization (QNM). We have referenced other bodies of work
[1] [2] [3] that have measured longitudinally the deployment of QNM; furthermore, we have examined those impacts to the various case study strings presented and ultimately arrived at the inclusion of labels beyond the TLD to be part of the CDMs. Understanding
the labels, their diversity, their context, etc provides valuable insights into current usage of the non-existent TLD and helps inform potential remediation/outreach efforts. The Root Cause report reiterates that sentiment. Furthermore, I’ll note that deployment
of various types of QNM techniques by resolvers also impacts name collision analysis at the second label – not all resolvers “chop off” the extra labels, some add random labels, which will impact any risk assessment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As for other changes within the DNS, there are several resources that clearly show additional impacts [4] [5].<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Matt<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[1] <a href="https://blog.verisign.com/security/maximizing-qname-minimization-a-new-chapter-in-dns-protocol-evolution/">
https://blog.verisign.com/security/maximizing-qname-minimization-a-new-chapter-in-dns-protocol-evolution/</a><o:p></o:p></p>
<p class="MsoNormal">[2] <a href="https://dnsthought.nlnetlabs.nl/#qnamemin">https://dnsthought.nlnetlabs.nl/#qnamemin</a><o:p></o:p></p>
<p class="MsoNormal">[3] https://research.utwente.nl/en/publications/a-first-look-at-qname-minimization-in-the-domain-name-system<o:p></o:p></p>
<p class="MsoNormal">[4] https://dash.harvard.edu/bitstream/handle/1/35979525/DNS_NBER_Working_Paper.pdf<o:p></o:p></p>
<p class="MsoNormal">[5] https://rssac002.root-servers.org/volume_udp_v_tcp_queries.html<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">NCAP-Discuss <ncap-discuss-bounces@icann.org> on behalf of Jeff Schmidt via NCAP-Discuss <ncap-discuss@icann.org><br>
<b>Reply-To: </b>Jeff Schmidt <jschmidt@jasadvisors.com><br>
<b>Date: </b>Monday, May 9, 2022 at 2:21 PM<br>
<b>To: </b>Jennifer Bryce <jennifer.bryce@icann.org>, "ncap-discuss@icann.org" <ncap-discuss@icann.org><br>
<b>Subject: </b>[EXTERNAL] Re: [NCAP-Discuss] FINAL REVIEW: NCAP Public Comment responses<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<table class="MsoNormalTable" border="0" cellpadding="0" width="1185" style="width:888.75pt;background:#F5ECCE">
<tbody>
<tr>
<td width="1175" style="width:881.25pt;padding:.75pt .75pt .75pt .75pt">
<p><strong><span style="font-family:"Calibri",sans-serif;color:#993300">Caution:</span></strong><span style="color:#993300"> </span><span style="color:black">This email originated from outside the organization. Do not click links or open attachments unless
you recognize the sender and know the content is safe. </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal">I have concerns about our responses to the RySG comments:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(1) Regarding “changes to the DNS traffic” we have bantered about how qname minimization, doh, local roots, and a handful of other technical changes may impact collisions but I don’t recall anything more rigorous than banter. The “we believe
there are changes to DNS traffic…” seems hollow, unsupported, and unactionable. Have we discussed this? Case Study 4.0 presents the issue at a high level but there are no conclusions vis-à-vis collisions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(2) The larger RySG comment (row 21 in the Excel) deserves more than the dismissal currently in our response. The RySG comment is fundamental to what this group is tasked to accomplish: do the Case Study and/or Perspective Study indicate
there is opportunity to make material improvements to existing procedures? Case Study 5.6 states that the conclusions the community came to a decade ago are “still sound.” We have generated lots of words, pretty graphs, statistics of all types, but I don’t
think we’ve made any clear statements about how to materially improve existing procedures.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think the RySG comment (and for that matter the OCTO comment) are canaries in the coalmine here that we should not merely dismiss or address defensively. These are sophisticated folks that made substantive comments. And these are the
folks that need our help to address this issue.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff<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-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>From:</b> NCAP-Discuss <ncap-discuss-bounces@icann.org> <b>
On Behalf Of </b>Jennifer Bryce<br>
<b>Sent:</b> Monday, May 9, 2022 8:08 AM<br>
<b>To:</b> ncap-discuss@icann.org<br>
<b>Subject:</b> [NCAP-Discuss] FINAL REVIEW: NCAP Public Comment responses<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Dear NCAP DG members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Heather has updated the public comment responses (linked below and Excel version attached) as per the feedback collected from the NCAP Discussion Group call on 27 April. The only lines that changed (beyond adding a “thank
you for your feedback”) were lines 14, 20, 21, and 22, as highlighted in the document.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB">FINAL CALL ON THE PUBLIC COMMENT RESPONSE DOCUMENT:</span></b><span lang="EN-GB"> Please review the highlighted changes. If you have any concerns, please raise them on this list before the 11 May Discussion Group call.
The finalized document will be included as an appendix in the NCAP Study 2 draft report.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Link to Google doc: <a href="https://docs.google.com/spreadsheets/d/1zOp-ClPdGqkmwE2xf0HhLg7SKvL3AFmz4ArSRuUF3BI/edit#gid=0">
https://docs.google.com/spreadsheets/d/1zOp-ClPdGqkmwE2xf0HhLg7SKvL3AFmz4ArSRuUF3BI/edit#gid=0</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Thanks,<br>
Jennifer<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-GB">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#A6A6A6">Jennifer Bryce<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Project Manager, Office of the Chief Technology Officer (OCTO)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Internet Corporation for Assigned Names and Numbers (ICANN)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#A6A6A6"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Skype: jennifer.bryce.icann<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Email: <a href="mailto:jennifer.bryce@icann.org">
jennifer.bryce@icann.org</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>