<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 15 (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: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;}
@font-face
{font-family:CourierNewPSMT;
panose-1:2 7 3 9 2 2 5 2 4 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{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><!--[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">And on tangential note around the effectiveness of outreach efforts, here is a summary of how we reduced the name collision footprint for .CBA:
<a href="https://forum.icann.org/lists/comments-name-collision-05aug13/msg00039.html">
https://forum.icann.org/lists/comments-name-collision-05aug13/msg00039.html</a><o:p></o:p></p>
<p class="MsoNormal"><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">NCAP-Discuss <ncap-discuss-bounces@icann.org> on behalf of Rubens Kuhl <rubensk@nic.br><br>
<b>Date: </b>Wednesday, April 29, 2020 at 5:25 PM<br>
<b>To: </b>"ncap-discuss@icann.org" <ncap-discuss@icann.org><br>
<b>Subject: </b>[EXTERNAL] Re: [NCAP-Discuss] [Ext] Re: Draft final Study 1 report<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Could you tell us more about the outreach efforts to those 45+ software developers in fixing the identified flaws ? <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"><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"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 29 Apr 2020, at 17:38, Thomas, Matthew <<a href="mailto:mthomas@verisign.com">mthomas@verisign.com</a>> wrote:<o:p></o:p></p>
</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">Can you please provide references to supporting data for the claim that “Other than that specific threat vector, commonplace security measures in Internet applications already handle man in the middle threats, regardless of being collision-related
or not.”?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">As a co-author on a publication that specifically conducted a systematic study of the robustness of internal network services under name collision attacks, that statement does not align with our findings. In fact, out of the 48 identified
exposed DNS-SD services, we found that nearly all (45) of them expose vulnerabilities in popular clients. Our results show that nearly all the exposed services have vulnerabilities (e.g. lack of server authentication by default, accept publicly-valid but previously
unseen TLS certificates by default, mix local-link and unicast DNS domain discovery, and do not enforce server authentication in PSK-based authentication, etc.), suggesting that the name collision problem broadly breaks common security assumptions made in
today’s internal network service clients.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Matt Thomas<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[1]<span class="apple-converted-space"> </span><a href="https://dl.acm.org/doi/pdf/10.1145/3133956.3134084"><span style="color:purple">https://dl.acm.org/doi/pdf/10.1145/3133956.3134084</span></a><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 style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt">From:<span class="apple-converted-space"> </span></span></b><span style="font-size:12.0pt">NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org">ncap-discuss-bounces@icann.org</a>> on behalf of
Rubens Kuhl <<a href="mailto:rubensk@nic.br">rubensk@nic.br</a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Wednesday, April 29, 2020 at 4:12 PM<br>
<b>To:<span class="apple-converted-space"> </span></b>"<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a>" <<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a>>, "<a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a>"
<<a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>[EXTERNAL] Re: [NCAP-Discuss] [Ext] Re: Draft final Study 1 report</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Anne,<span class="apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Most of what you posted is more of the same and I'll just refer people to my previous comments on them, available on both list archives. On the man in the middle issue, this was already identified by SAC 057, and had its most prominent
threat vector mitigated by measures by both the ICANN collision framework and CA/B Forum guidelines that now don't allow certificates to not delegated TLDs. Other than that specific threat vector, commonplace security measures in Internet applications already
handle man in the middle threats, regardless of being collision-related or not. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Rubens<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">On 29 Apr 2020, at 15:50, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com"><span style="color:purple">AAikman@lrrc.com</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Thanks Rubens. I guess I took the comments as a potential need to work on the design of Study 2. Perhaps OCTO staff can clarify the scope of Study 1 in
this regard? Did OCTO identify the independent contractor as a name collision expert? Or was the assignment limited to gathering existing information and identifying gaps in the data?</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">As you know, the Board has posed questions to the SSAC that cannot be answered without further research. The NCAP Discussion Group has been working on how
those questions might be addressed and properly answered in all of its recent weekly calls. Further, Rod Rasmussen recently sent out an email confirming that the SSAC Work Party is itself a separate body from the Name Collision Analysis Project and will
need to consider its responses to the Board’s questions and the degree to which more data may be needed in order to respond to those questions. Interestingly, some data has come in recently from ICANN’s own server indicating that there are voluminous queries
going to the non-existent .home and .corp TLDs (in addition to .lan and others). It therefore seems very superficial (and even inaccurate based on the data) to conclude that 90 day controlled interruption is adequate to address all name collision issues.
This is particularly true because “Man in the Middle” interceptions of the misguided queries from the 2012 round were apparently never measured. As you know, these Man in the Middle interceptions provide fertile ground for fraud and other harm to consumers.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Public comment on the Sub Pro “Initial Report” name collisions summary emphasizes the need to “defer to the SSAC”. In some cases, it also says, “Defer to
the NCAP”. For well over a year, we have been hearing from some individuals in Sub Pro Leadership that the name collision analysis “isn’t going anywhere” and that our Sub Pro deliberations should not “be held up” waiting for that to happen. Nevertheless,
so far we have a tentative recommendation that ICANN develop a “Do Not Apply” list and it’s clear that this work can be part of the NCAP and SSAC work that is already underway. A “DO NOT APPLY” list and/or a test for measuring the name collision risk of a
particular string as a “gating mechanism” at the time of application would certainly be useful. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Accordingly, I have always maintained that Sub Pro should be “dovetailing” its efforts with those of NCAP and the SSAC so that we all have our “ducks in a
row” in time for the next round. The ICANN Board specifically stated in its public comment on the “Initial Report” from Sub Pro that this issue presented an opportunity for us to work across the community and work together. For some reason, there is continuing
resistance to that approach and Sub Pro Leadership continues to cast doubt on the need for continued work of the NCAP and the SSAC in this arena. In my view, that approach will not get us to the next round any faster and will, in fact, have the opposite effect
as we risk setting up another “bottleneck” at the Board level where they may be getting conflicting advice coming from different arms of the community. (This general phenomenon of not working things out before conflicts get to the Board level is ICANN’s biggest
weakness in terms of organizational effectiveness and it causes immense delays.)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Based on the public comment previously received by Sub Pro as well as the Board questions to the SSAC, we need to work together as requested by the Board,
rather than stubbornly resisting the further study of these risks. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D">Anne</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org"><span style="color:purple">ncap-discuss-bounces@icann.org</span></a>><span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Rubens Kuhl<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Tuesday, April 28, 2020 3:43 PM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a>;<span class="apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org"><span style="color:purple">ncap-discuss@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [NCAP-Discuss] [Ext] Re: Draft final Study 1 report<br>
<b>Importance:</b><span class="apple-converted-space"> </span>High<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Anne,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The exact quote from Karen's report is as this:</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">"Given these findings, the recommendation is that Studies 2 and 3 should not be performed as currently designed. Regarding Study 2, analyzing datasets is unlikely to identify
significant root causes for name collisions that have not already been identified. New causes for name collisions are far more likely to be found by investigating TLD candidates for potential delegation on a case by case basis. Regarding Study 3, the review
of prior work has not identified any new mitigation strategies for name collisions to be tested. Also, controlled interruption has already proven an effective mitigation strategy. Without a compelling new mitigation strategy to consider, Study 3 does not seem
to be needed at this time.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">All of that being said, this does not mean further study should not be conducted into name collision risks and the feasibility of potentially delegating additional domains
that are likely to cause name collisions. However, the proposals for Studies 2 and 3 do not seem to still be effective ways of achieving those goals."</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">I think her words are self-explanatory of her views, which have already been endorsed in the NCAP mailing list by Jeff Schimdt. </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Rubens</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">On 28 Apr 2020, at 19:14, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com"><span style="color:purple">AAikman@lrrc.com</span></a>> wrote:</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">HI Jeff,</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">I listened to last night’s Sub Pro call (which I was unable to attend). In that call, you advised the Sub Pro Working Group verbally that the independent contractor for NCAP Study 1, Karen Scarfone, had made
a Study 1 recommendation against proceeding to Study 2 and 3. You also stated that “not everyone” in the NCAP Discussion Group agrees with Karen’s recommendation that Study 2 and 3 should not proceed.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">I can’t quite figure out why you believe that Karen made such a recommendation. It would be good if you could clarify this before the April 30 call on Name Collisions. Please reply to all.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thank you,</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<div>
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org"><span style="color:purple">ncap-discuss-bounces@icann.org</span></a>><span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Jeff Neuman<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Monday, April 27, 2020 8:59 AM<br>
<b>To:</b><span class="apple-converted-space"> </span>Matt Larson <<a href="mailto:matt.larson@icann.org"><span style="color:purple">matt.larson@icann.org</span></a>><br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org"><span style="color:purple">ncap-discuss@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [NCAP-Discuss] [Ext] Re: Draft final Study 1 report<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:Helvetica">[EXTERNAL]</span></strong><o:p></o:p></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="0" width="100%" align="center">
</span></div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Thanks Matt. I forwarded to the SubPro Group your original e-mail which contained the study and your cover note.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Jeff Neuman</span></b><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Senior Vice President </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Com Laude | Valideus</span></b><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">D: +1.703.635.7514</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">E:<span class="apple-converted-space"> </span><u><span style="color:#0563C1"><a href="mailto:jeff.neuman@comlaude.com"><span style="color:purple">jeff.neuman@comlaude.com</span></a></span></u></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<div>
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>Matt Larson <<a href="mailto:matt.larson@icann.org"><span style="color:purple">matt.larson@icann.org</span></a>><span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Monday, April 27, 2020 11:29 AM<br>
<b>To:</b><span class="apple-converted-space"> </span>Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com"><span style="color:purple">jeff.neuman@comlaude.com</span></a>><br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org"><span style="color:purple">ncap-discuss@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [NCAP-Discuss] [Ext] Re: Draft final Study 1 report<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Hi, Jeff, everyone.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal">On Apr 27, 2020, at 8:01 AM, Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com"><span style="color:purple">jeff.neuman@comlaude.com</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"CourierNewPSMT",serif">The SubPro Working Group is discussing the issue of Name Collisions on its Thursday call. Is this list public? And if so, can I post the latest document to the SubPro list
so that they can see the current state of the studies? I would be happy to post other comments you all have to the report as well that you would want shared.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">This list has public archives, so anyone can see my message with the current draft attached. If you want to share on the SubPro list, could I please suggest that you point people to my message in the archives rather than send the document
itself? That link is<span class="apple-converted-space"> </span><a href="https://secure-web.cisco.com/12s-XmHv6tay6qCQIJYTu8_F-noUYbIWbs1i82g73Nur9bdm_txOf64TsI80sGO4Rn1MVTlbUxK4l0kodfyRBauI2doirk07h-gbTtYw8-TAfx5C6KTiLjv2nodiSc5BPy7_i6WvA1QGrJ9MB856DYr21i4tozXZLhfL9g-3URYruQnyoWuWtnXR-d9PY55cdfDRU52wKK4hSZB6ekLSdk_ZzqiUmJmC4Gqd1nj4NNeggOjAtsByvSEFXW5H6aoO-AERhVaShfOqaHY9zZS1SxA/https%3A%2F%2Fmm.icann.org%2Fpipermail%2Fncap-discuss%2F2020-April%2F000275.html"><span style="color:purple">https://mm.icann.org/pipermail/ncap-discuss/2020-April/000275.html</span></a>.
Sharing the document that way will hopefully help keep the context clear, specifically, that this report is not final.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Matt<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="0" width="100%" align="center">
</span></div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the
intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any
responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of
its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company
registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville
Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office
at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see<span class="apple-converted-space"> </span><a href="https://secure-web.cisco.com/13qQt5jQRheG-NeQvIGsZLJCqd9t3miWyoKOaOguQyS_PP8wSbDl54cgl1jc_b2_5N362RQkuosGDaBHb8xAMCw2y5FsSsg8SjiI0vovDkWpOu2VoLWp46IBI4iKJstglHBJUlfYKcMMVKaFn_yIDDsWvG5b_yQVIldTX6uec-9TZK9DZPDWLXtSNmavev09LHhLzFBZ0gmawDvZAacRZU8i-jSFBQqn03UIACnIH_4OrSsWjOyHY3OwpNU2_V9rvXqohd2W7FA5OF04Bk5_ESw/https%3A%2F%2Fcomlaude.com%2F" target="_blank"><span style="color:purple">www.comlaude.com</span></a></span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="0" width="100%" align="center">
</span></div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><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>
</span><span style="font-size:9.0pt;font-family:Helvetica">_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org"><span style="color:purple">NCAP-Discuss@icann.org</span></a><br>
<a href="https://secure-web.cisco.com/1p9LliPd16wIS-jKiLAqpSy51NZdO3SqxTO1FlddpAsx-BWS4lDMeiwrJtuZLppzcJ5ZSCIqRKhtjq75ITQoj4k62Ci482xInI3ZRv6I94lszbnafmTic2wt7LVdYZcRhhO8lzMo54_zjtvE0rcy5I6MEK_dWyqXTsrh0vLh1zuYti31XGb6bp9l7SukfxYahrbTD1uv07XQ3syPngXMB8AdoER4JYFLqrpP8mnm3cCR5orCBHZADzEKvZ6bpY57LU4tNb2Du02nZFLyJdJCJcw/https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fncap-discuss"><span style="color:purple">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://secure-web.cisco.com/1v6hGhDyy1bpWr4YJdWaQQ9Dlhl5ZPJ-rmEuWY695D0CccOQY_MnS_L_18bsmt0ydqRDO0VBTZlezx8uF87YhizOVGCUxshPvx2iUlP83R40Ztrxz_vu9uMLn-eed60XNCjzp7M83Ff-wHEZJWzCiT5TgaA9mw6xGSpG8UDOvtwd7EJ2hPoCmSqmrq-apT7wuN1A5pQC4BGXLhjUG13DSKSDDy_XNHoImlq7T4-tN3tKQ-S_rgmgpTEnAnGdMbaN4_-QFUZv540StI_jW70lBpQ/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy"><span style="color:purple">https://www.icann.org/privacy/policy</span></a>)
and the website Terms of Service (<a href="https://secure-web.cisco.com/1uB-uUY8Gtmei5TmYMbxU2XfS0NXt4PnlPMSwxisjbUpwYeSp3gGr0E4pq7qnEcP4ROJ-Brq9MTF1wXGVi-Y05FtSBI2TM2d61ecsBH-fYFE4mYNzJewPyVYt6SDmgCZFGUJW95puyB5buawWEamFgwOiZxY2aKGlZOB_bT34_XJf3wwelO0HOZ6qG0BotuvH0o1G2RYM3dFXZ5pniYBtkExS4GdbZ1MQ7kwG_Ws-U8pnJS93vFn_tww1Y6PsUdu0Zn4xWUXyXwqxBSnioxv3XQ/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos"><span style="color:purple">https://www.icann.org/privacy/tos</span></a>).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><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.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>