<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.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" style="word-wrap:break-word;overflow-wrap: break-word;-webkit-nbsp-mode: space;line-break:after-white-space">
<div class="WordSection1">
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">All,<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">We’ve had a long-standing action item to track down an error in the Name Collision definition and scoping document. I tracked down the error and the proposed correction based on the NCAP DG recording
[1] from the May 13, 2020 meeting [2]. I propose we make a small correction in the final Study 2 report, specifically in question 1 of the Board Questions, that highlights the erroneous inclusion of a scoping item. The correction is straight forward (we simply
state the item should not be included). The change should not impact any of the existing Study 2 work. I do not foresee this as a contentious item, but more of a formality and being thorough and that our work is accurate and complete.<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">Details 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">The original NCAP Name Collision definition was approved to be the following (the full definition and scoping document can be found here [3]):<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">“Name collision refers to the situation in which a name that is used in one namespace may be used in a different namespace, where users, software, or other functions in that domain may misinterpret
it. In the context of top level domains, the term ‘name collision’ refers to the situation in which a name that is used in the global Domain Name System (DNS) namespace defined in the root zone as published by the root zone management (RZM) partners ICANN
and VeriSign (the RZM namespace) may be used in a different namespace (non-RZM), where users, software, or other functions in that domain may misinterpret it.”<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">The document contains a set of examples that are in-scope and out-of-scope data subjects. One of the examples in the out-of-scope section should not be included.<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">It was noted in the May 13, 2020 NCAP DG meeting that an item was erroneously included in the “In scope but not intended to be the subject of data studies” section as it was in direct conflict
with the definition above. The error was item B.c in which: “Registrant Alice uses EXAMPLE.COM and the lets the registration expire. Registrant Bob the registers and delegates EXAMPLE.COM. Traffic intended for Alice’s use of EXAMPLE.COM is now received
by Bob’s use of EXAMPLE.COM”.<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">By the definition provided, B.c cannot be included because it must be in a different namespace – “used in a different namespace (non-RZM)”. A re-registration, by the above definition, is not a
different namespace.<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">NCAP Co-chair<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">[1] <a href="https://icann.zoom.us/rec/share/2PZaELveqVJOG6-O9HDPZPUdQaHKX6a8hnVNr_IFzUvO9VBO3O4B1cfdh-I3kk_W" title="https://icann.zoom.us/rec/share/2PZaELveqVJOG6-O9HDPZPUdQaHKX6a8hnVNr_IFzUvO9VBO3O4B1cfdh-I3kk_W">https://icann.zoom.us/rec/share/2PZaELveqVJOG6-O9HDPZPUdQaHKX6a8hnVNr_IFzUvO9VBO3O4B1cfdh-I3kk_W</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">[2] <a href="https://community.icann.org/pages/viewpage.action?pageId=132941347" title="https://community.icann.org/pages/viewpage.action?pageId=132941347">https://community.icann.org/pages/viewpage.action?pageId=132941347</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black">[3]<a href="https://community.icann.org/display/NCAP/NCAP+Working+Documents?preview=/79437474/111387704/Definition%20of%20Name%20Collision%20and%20Scope%20of%20Work%20for%20the%20NCAP.pdf" title="https://community.icann.org/display/NCAP/NCAP+Working+Documents?preview=/79437474/111387704/Definition%20of%20Name%20Collision%20and%20Scope%20of%20Work%20for%20the%20NCAP.pdf">https://community.icann.org/display/NCAP/NCAP+Working+Documents?preview=/79437474/111387704/Definition%20of%20Name%20Collision%20and%20Scope%20of%20Work%20for%20the%20NCAP.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span style="font-size:13.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>