<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="ltr">
<div></div>
<div data-ogsc="" style="">
<div>Anne,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I would just offer the fact that just because there is additional data does not mean that there is a gap in data to answer the questions before us. There will always be data to gather somewhere and more and more of it every day that could be
generated. But that doesn’t mean that there is an identified gap in data to do our work. </div>
<div><br>
</div>
<div class="ms-outlook-ios-signature" id="ms-outlook-mobile-signature">Get <a href="https://aka.ms/o0ukef" data-ogsc="" style="">
Outlook for iOS</a></div>
</div>
<div id="id-3585e64c-564e-4bf3-84f9-fb51612b0d4c" class="ms-outlook-mobile-reference-message">
<hr style="display: inline-block; width: 98%; font-family: -webkit-standard; font-size: 12pt; color: rgb(0, 0, 0);" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"><b>From:</b> NCAP-Discuss <ncap-discuss-bounces@icann.org> on behalf of Aikman-Scalese, Anne <AAikman@lrrc.com><br>
<b>Sent:</b> Wednesday, May 6, 2020 2:27 PM<br>
<b>To:</b> Karen Scarfone<br>
<b>Cc:</b> NCAP Discussion Group<br>
<b>Subject:</b> Re: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)
<div> </div>
</font></div>
<meta content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:Helvetica}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:HelveticaNeue}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
color:#1F3864}
p.msonormal0, li.msonormal0, div.msonormal0
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif}
span.PlainTextChar
{font-family:"Calibri",sans-serif;
color:#1F3864}
span.EmailStyle20
{font-family:"Calibri",sans-serif;
color:windowtext}
span.EmailStyle22
{color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">OK – I don’t have technical background but given the changes in the internet since 2012, it seems there would be datasets out there that would be helpful. For example, the data that was just retrieved
from the ICANN server?</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thank you,</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Anne</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Karen Scarfone <karen@scarfonecybersecurity.com>
<br>
<b>Sent:</b> Wednesday, May 6, 2020 9:36 AM<br>
<b>To:</b> Aikman-Scalese, Anne <AAikman@lrrc.com><br>
<b>Cc:</b> NCAP Discussion Group <ncap-discuss@icann.org><br>
<b>Subject:</b> Re: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: black;">[EXTERNAL]</span></strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: black;"></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt; font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal">Anne,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color: black;">I didn’t find any dataset issues or gaps, so I don’t have a list of other datasets that would be needed. I am going to add a finding to that effect.</span><span style="font-size: 10.5pt; font-family: HelveticaNeue; color: black;"></span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Karen</p>
<p class="MsoNormal"> </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: 12pt; color: black;">From: </span>
</b><span style="font-size: 12pt; color: black;">"Aikman-Scalese, Anne" <<a href="mailto:AAikman@lrrc.com" data-ogsc="" style="">AAikman@lrrc.com</a>><br>
<b>Date: </b>Tuesday, May 5, 2020 at 6:21 PM<br>
<b>To: </b>Karen Scarfone <<a href="mailto:karen@scarfonecybersecurity.com" data-ogsc="" style="">karen@scarfonecybersecurity.com</a>><br>
<b>Cc: </b>NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" data-ogsc="" style="">ncap-discuss@icann.org</a>><br>
<b>Subject: </b>RE: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thanks Karen. I may have misunderstood the discussion on the list, but I think the RFP specifies the following requirement which is independent of the recommendation whether or not to proceed:</span></p>
<p class="MsoPlainText" data-ogsc="" style=""><b>creation of a list of additional data sets that would be required to successfully complete Studies 2 and 3.</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b> </b></p>
<p class="MsoPlainText" data-ogsc="" style="">Anne</p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Karen Scarfone <<a href="mailto:karen@scarfonecybersecurity.com" data-ogsc="" style="">karen@scarfonecybersecurity.com</a>>
<br>
<b>Sent:</b> Tuesday, May 5, 2020 12:15 PM<br>
<b>To:</b> Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" data-ogsc="" style="">AAikman@lrrc.com</a>><br>
<b>Cc:</b> NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" data-ogsc="" style="">ncap-discuss@icann.org</a>><br>
<b>Subject:</b> Re: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: black;">[EXTERNAL]</span></strong></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt; font-family:"Times New Roman",serif">
<hr size="1" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal">Anne,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I was asked to make a recommendation based not only on dataset availability, but also “the results of the survey of prior work.” I felt that the survey of prior work indicated that Studies 2 and 3 should not go forward as designed, so dataset
access was irrelevant. Actually, I didn’t find significant issues in obtaining the datasets. In an earlier draft of the report, I had an explicit finding about dataset access not being an issue, but that seemed superfluous, so I deleted it. I can add it back
to the report if that would be clearer.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Karen</p>
<p class="MsoNormal"> </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: 12pt; color: black;">From: </span>
</b><span style="font-size: 12pt; color: black;">NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" data-ogsc="" style="">ncap-discuss-bounces@icann.org</a>> on behalf of "Aikman-Scalese, Anne" <<a href="mailto:AAikman@lrrc.com" data-ogsc="" style="">AAikman@lrrc.com</a>><br>
<b>Date: </b>Friday, May 1, 2020 at 3:37 PM<br>
<b>To: </b>Matt Larson <<a href="mailto:matt.larson@icann.org" data-ogsc="" style="">matt.larson@icann.org</a>><br>
<b>Cc: </b>NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" data-ogsc="" style="">ncap-discuss@icann.org</a>><br>
<b>Subject: </b>Re: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoPlainText" data-ogsc="" style=""><b>Scope of Study 1 and the Unanswered Board Questions</b></p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Hi all - I checked the ICANN RFP in relation to the scope of Study 1. It clearly looks for the consultant's recommendation as to whether or not to proceed to Studies 2 and 3. In fact, the ICANN RFP actually specifically
suggests to the bidders that the consultant might conclude “that it would not be possible to obtain the data necessary to successfully complete Studies 2 and 3”. It appears that Karen has concluded it would not be possible to obtain the data sets. However,
there are others on the list who disagree regarding the ability to obtain the data. In addition, the SSAC is charged with answering the ICANN Board’s questions regarding certain topics that are only addressed in Study 2. So what is the Discussion Group’s
view as to how Study 2 might be redesigned in a way that would permit these answers to be provided to the Board? (See Jim’s chart on this point.)</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style=""><b>Effectiveness of Controlled Interruption to Mitigate Harm</b></p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">In recommending against Study 2 and 3 as currently designed, Karen’s report further states “Also, controlled interruption has already proven an effective mitigation strategy.” Regarding the standard for reporting
in the last round, see the following from the icann.org website “If your system is suffering
<b>demonstrably severe harm</b> (emphasis added) as a consequence of name collision, please fill in the form below to report the incident<b>. </b><strong><span style="font-family:"Calibri",sans-serif; font-weight:normal">ICANN will initiate an emergency response
for name collision reports only where there is a reasonable belief that the name collision presents a</span></strong><strong><span style="font-family:"Calibri",sans-serif"> clear and present danger to human life.”
</span></strong><strong><span style="font-family:"Calibri",sans-serif; font-weight:normal">In particular in light of the current level of community concern over DNS Abuse, it appears that the question of “effective mitigation strategy” cannot be limited to
“demonstrably severe harm” or “clear and present danger to human life.” Further, recent data from ICANN’s server suggests that users have not been effectively “educated” to avoid non-existent TLDs. There has been no suggestion that Man in the Middle consumer
protection issues such as fraud resulting from name collisions should be reported to ICANN. (The reporting form appears to have been addressed to IT professionals.)</span></strong></p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style=""><b>Need for Useful Name Collision Tools for the Next Round – DO NOT APPLY List and Test for Level of Risk associated with an Applied-For String</b></p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">All that said, in particular after yesterdays’ Sub Pro call, I’m personally focused on the fact that the Sub Pro WG will be formally recommending to the GNSO (and then ultimately to the Board) (A) the development
of a “Do Not Apply” list and (B) a reliable test for Name Collision strings to be identified for the next round that would be used to test each applied-for string before delegation to determine whether the string is “high risk”, “medium risk”, or “low risk”.
Jeff Neuman mentioned these useful tools in the last NCAP call and there was discussion around redesigning Study 2 for the purpose of arriving at practical tools that would fulfill these roles in the next round. Call me crazy, but it appears that the logical
place for these tools to be developed is within the Name Collision Analysis Project.</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Looking forward to further discussion in next Wednesday’s call,</p>
<p class="MsoPlainText" data-ogsc="" style="">Anne</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Section of RFP related to Scope:</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style=""><b>"The SSAC proposal calls for three studies investigating name collisions to be performed consecutively. Study 1 will serve as a foundation for Studies 2 and 3. This RFP covers only Study 1 .However, Study 1 will
provide insight in Studies 2 and 3, and an important outcome and deliverable of Study 1 is a recommendation on whether or not to proceed with Studies 2 and 3.(Study 1 might conclude, for example, that it would not be possible to obtain the data necessary to
successfully complete Studies 2 and 3.)"</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b> </b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b>The goals of Study 1 are:</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b>1. Production of a summary report on the topic of name collision that brings forth important knowledge from prior work in the area. The report will be a primer for those new to the subject. The report will be
based on an examination of all relevant prior work on the issue of name collisions.</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b>2. Creation of a list of datasets used in past name collision studies; an identification of gaps 2, if any; and creation of a list of additional data sets that would be required to successfully complete Studies
2 and 3.</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b>3. A recommendation if Studies 2 and 3 should be performed based on the results of the survey of prior work and the availability of data sets.”</b></p>
<p class="MsoPlainText" data-ogsc="" style=""><b> </b></p>
<p class="MsoPlainText" data-ogsc="" style="">-----Original Message-----<br>
From: NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" data-ogsc="" style="">ncap-discuss-bounces@icann.org</a>> On Behalf Of Matt Larson<br>
Sent: Friday, May 1, 2020 9:57 AM<br>
To: Jeff Schmidt via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org" data-ogsc="" style="">ncap-discuss@icann.org</a>><br>
Subject: [NCAP-Discuss] Comment deadline extended (was Re: Draft final Study 1 report)</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">[EXTERNAL]</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Dear colleagues,</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Given the ongoing discussion on the list, I am extending the deadline for your comments on the draft final Study 1 report to next Wednesday, 6 May.</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">After that, Karen will revise the report and we will open a Public Comment.</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Thanks,</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">Matt</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">> On Apr 24, 2020, at 11:03 AM, Matt Larson <<a href="mailto:matt.larson@icann.org" data-ogsc="" style=""><span style="color: rgb(31, 56, 100); text-decoration: none;">matt.larson@icann.org</span></a>> wrote:</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> Dear colleagues,</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> Attached is Karen's draft of the final version of Study 1. Changes since the last version are highlighted, but the significant updates are in Section 5 (Datasets) and the addition of an executive summary and a
conclusion.</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> OCTO has told Karen all along that she should feel free to reach whatever conclusion she felt warranted by the research she's done. We have not attempted to undermine her professional integrity by leading her
in any particular direction.</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> We'd be grateful for your review and comment. We'll be following the same process as we did with the draft version of the report: this group has a chance to comment first and then the report will go out for a
formal Public Comment.</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> In order to stay on schedule to deliver the final report to the Board by 30 June as we've promised, we need any feedback from this group by next Friday, 1 May.</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> Thanks,</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> Matt</p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style="">> <NCAP Phase 1 Report Draft 20200422-for-DG-review.docx></p>
<p class="MsoPlainText" data-ogsc="" style="">> </p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">_______________________________________________</p>
<p class="MsoPlainText" data-ogsc="" style="">NCAP-Discuss mailing list</p>
<p class="MsoPlainText" data-ogsc="" style=""><a href="mailto:NCAP-Discuss@icann.org" data-ogsc="" style=""><span style="color: rgb(31, 56, 100); text-decoration: none;">NCAP-Discuss@icann.org</span></a></p>
<p class="MsoPlainText" data-ogsc="" style=""><a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" data-ogsc="" style=""><span style="color: rgb(31, 56, 100); text-decoration: none;">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a></p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoPlainText" data-ogsc="" style="">_______________________________________________</p>
<p class="MsoPlainText" data-ogsc="" style="">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://www.icann.org/privacy/policy" data-ogsc="" style=""><span style="color: rgb(31, 56, 100); text-decoration: none;">https://www.icann.org/privacy/policy</span></a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" data-ogsc="" style=""><span style="color: rgb(31, 56, 100); text-decoration: none;">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.</p>
<p class="MsoPlainText" data-ogsc="" style=""> </p>
<p class="MsoNormal"> </p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size: 7.5pt; font-family: Arial, sans-serif;"><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></p>
<p class="MsoNormal"> </p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size: 7.5pt; font-family: Arial, sans-serif;"><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></p>
</div>
<br>
<hr>
<font face="Arial" size="1"><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>
</font></div>
</div>
<hr>
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
<a href="https://comlaude.com" target="_blank">www.comlaude.com</a>
</body>
</html>