<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:Wingdings;
panose-1:5 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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{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;}
/* List Definitions */
@list l0
{mso-list-id:223417150;
mso-list-template-ids:-903435616;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1893539023;
mso-list-type:hybrid;
mso-list-template-ids:-1009883998 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">NCAP DG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">I wanted to share with you the responses received from ICANN OCTO for a request to provide some technical expertise around any known technical challenges or problems with the proposed delegation
strategies related to the passive measurement system (e.g., Ad measurements). <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">Matt Thomas<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">ICANN OCTO first response below:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">Thank you for your request for OCTO to preview the NCAP delegation proposal. As you discuss in the proposal, all the configurations would represent a change from the current behavior (the root
sending authoritative NXDOMAIN replies). Changing this behavior could potentially cause disruption to some systems, so the benefit of this new behavior has to be weighed against the risk of disruption. We note that some in the DNS-OARC technical community
have brought up similar issues in their Mattermost discussion system.</span><span style="color:black"><br>
<br>
</span><span style="font-size:13.5pt;color:black">However, the NCAP delegation proposal says nothing concrete about the expected benefits. The introduction talks about “name collision assessment purposes” and “collision measurement”, but doesn't say what benefit
will come from them. Based on the text of the proposal and also based on further context we are aware of from following NCAP, the purpose of this proposal is to collect additional data that will later be analyzed for possible value. However, we have yet to
see a description that goes into specifics on the planned use for the data. Our opinion is therefore that since specific benefits arising from gathering additional data have not been specified, the possible risk of disruption from the changed behavior is not
justified.</span><span style="color:black"><br>
<br>
</span><span style="font-size:13.5pt;color:black">Further, OCTO notes that the measurements taken from such delegations are more easily gamed than measurements taken from captures at the root servers. (We do recognize the difficulty involved in capturing data
at the root because of the large number of instances.) That is, someone who wants to sway the outcome of the measurements will be more able to do so if the TLDs in question are delegated to a small number of authoritative name servers. The proposal from NCAP
is silent on the measurement problems that the proposal will suffer from and how these problems might be addressed.</span><span style="color:black"><br>
<br>
</span><span style="font-size:13.5pt;color:black">We would like to take this opportunity to express our concern that this proposal represents a departure from controlled interruption, a technique that has worked successfully for over 1200 new delegations in
the past decade. Proposals for divergence from controlled interruption that could cause new risks of disruption need to be justified with specific benefits.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">----<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Below is a follow up response from ICANN OCTO after sending some additional context about the measurement proposal:<o:p></o:p></span></p>
<p class="MsoNormal">----<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">After reviewing the ad measurement proposal for additional context, we stand by our original response. Our position is that any change to root zone operational behavior first requires an analysis
to determine if the risk is worth the intended benefits. The proposal would result in additional data being collected without specifying how the data will be interpreted or even what the benefits of having the additional data would be. As a result, the proposal
does not supply enough information to perform a risk analysis, so the risk of any changed behavior is not justified.</span><span style="color:black"><br>
<br>
</span><span style="font-size:13.5pt;color:black">Specifically, the ad measurement proposal describes a new measurement of what percentage of ads referencing a new TLD string cause DNS queries to be received at the TLD’s authoritative servers, but does not
describe how results are to be interpreted. The proposal calls for a risk assessment based on both passive data collection and ad-based measurement data, but does not describe the specific criteria for the risk assessment. On the contrary, the proposal specifically
states that the criteria need to be developed.</span><span style="color:black"><br>
<br>
</span><span style="font-size:13.5pt;color:black">We repeat the conclusion from our initial response, which we believe is still valid, if not even more so in light of the additional ad measurement proposal: both passive data collection and ad measurement represent
a departure from controlled interruption, a technique that has worked successfully for over 1200 new delegations in the past decade. Proposals for divergence from controlled interruption that could cause new risks of disruption need to be justified with specific
benefits.</span><span style="font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>