<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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.gmaildefault
{mso-style-name:gmail_default;}
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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thanks, Steve, we will get this added to the index of relevant resources. Note we have updated the settings of the google doc so that anyone can add comments. If you spot anything else
that is missing, please feel free to suggest in the document itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Caitlin, Berry and Marika<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Steve Crocker <steve@shinkuro.com><br>
<b>Date: </b>Monday, 27 September 2021 at 18:33<br>
<b>To: </b>Michael Palage <michael@palage.com><br>
<b>Cc: </b>"gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org><br>
<b>Subject: </b>Re: [GNSO-Accuracy-ST] Welcome<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Mike,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Thanks for taking this on.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">I glanced quickly at the compilation of resources. I did not see a reference to SAC 058, "SSAC Report on Domain Name Registration Data Validation." I think this
report, and in particular, Section 3, on pages 7-8, titled Taxonomy of Validation , are a solid basis for the work of this group.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Here is the text of section 3.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">3. Taxonomy of Validation</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Verification, validation and resolution have been used interchangeably in various literature on this topic. We choose “validation” to refer to the assessment of data
as described by this document. Verification in this document refers to the process of validating. Resolution has an entirely different technical meaning that is out of scope for this document. The SSAC asserts there are three types of validation for elements
of the registration data.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">1. Syntactic Validation refers to the assessment of data with the intent to ensure that they satisfy specified syntactic constraints, conform to specified data standards,
and are transformed and formatted properly for their intended use. For example, if the data element is expected to be an email address is it formatted as an email address? In general, it is expected that syntactic validation checks would be entirely automated
and could be executed inline with a registration process, follow up information reviews, and whenever registration data changes. (</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">See Edelman, B. (2002) Large-Scale Intentional
Invalid WHOIS Data: A Case Study of "NicGod Productions" / "Domains For Sale” Cambridge, MA: Harvard University at
<a href="https://urldefense.com/v3/__http:/cyber.law.harvard.edu/archived_content/people/edelman/invalid-whois/__;!!PtGJab4!u5NwC2cny3f54eyaS5KogdELkowtqrc57gWQt0SEMd4ZGCZTcXc90_284soTrl_vi5OWsKhGXA$">
http://cyber.law.harvard.edu/archived_content/people/edelman/invalid-whois/ [cyber.law.harvard.edu]</a>)</span><span style="font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">2. Operational Validation refers to the assessment of data for their intended use in their routine functions. Examples of operational validation include 1) checking
that an email address or phone number can receive email or phone calls; 2) checking that a postal address can receive postal mail; 3) checking that the data entered are self-consistent, i.e. that all data are logically consistent with all other data. It is
expected that many operational validation checks would be automated and some could be executed inline with a registration process.<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">3. Identity validation refers to the assessment that the data corresponds to the real world identity of the entity. It involves checking that a data item correctly
represents the real world identity for the registrant. In general, identity validation checks are expected to require some manual intervention.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><span class="gmaildefault"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Cheers,</span></span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="gmaildefault"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Steve</span></span><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">On Mon, Sep 27, 2021 at 11:56 AM Michael Palage <<a href="mailto:michael@palage.com">michael@palage.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p style="margin:0cm"><span lang="EN-US">Dear Scoping Team members,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">I want to start by personally thanking everyone for volunteering for this effort. As you may have heard, I’ve recently been appointed by the GNSO Council to lead this effort.
<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">While I know many of you know me, there are a couple of new faces so I would like to give a brief background about myself and my motivation for volunteering as chair.<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">I have been a participant in the ICANN multistakeholder model (MSM) now for almost 23 years and during that time I have served in a number of capacities, including the Chair of ICANN’s second ever Working Group, aptly
name Working Group B. Suffice it to say that over the years I have had a front row seat watching the continued evolution of the Policy Development Process. During this time I have actively participated in a number of stakeholder groups, e.g. Registrars, Registries,
Business, IPC, and ALAC. I believe this diverse background allows me see and understand topics from multiple perspectives, and will help me to ensure that all points of view are heard on these complex issues. As required by the rules, I must remain neutral
in all of the discussions, but remaining neutral also means I have a duty to make sure that all relevant viewpoints are heard and addressed.<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">My primary motivation in volunteering for this effort is my concern about the ongoing sustainability of the MSM which I have devoted the past 23 years of my professional life trying to safeguard. Both those within the
ICANN community, as well as others outside of it, have expressed to me their dissatisfaction with the MSM and how inefficient it can be. And although they raise some good points, I firmly believe that we can always do better and that we should never give
up on improving the MSM.<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">When I first got involved in ICANN one of the strongest selling points of the MSM was that it could respond more quickly to market dynamics than traditional government/regulatory forces. My concern is that I see a growing
number of my ICANN colleagues seemingly giving up on the MSM model and taking their issues directly to national governments or International Organizations rather than focusing on getting things done through the ICANN MSM. It is as if there is a perception
that governments can more efficiently respond to market dynamics than can the MSM. I believe there needs to exist a symbiotic relationship between the ICANN policy development process and national legislative initiatives. This is all part of the grand public-private
partnership which is ICANN.<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">The best way to help the efficiency of the MSM, in my humble view, is to become a part of it to demonstrate once again the value of the public-private partnership and to hopefully show that we can respond to market and
regulatory demands. However, the ultimate success of this group is not driven by the chair, but rather by the cooperation and willingness of the Working Group members to be able to listen to all sides of an issues, understand the problems being faced, and
to resolve to address those problems. This will of course necessitate compromise on all sides where appropriate.
<o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black">I’ve asked the staff support team to help me in putting together a short survey which we will be circulating shortly in the next 24-48 hours. I really need everyone to complete this survey before
our first call.</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black">Finally, as you may have seen, we already have a workspace (see
</span><span lang="EN-US"><a href="https://community.icann.org/x/hQIuCg" target="_blank">https://community.icann.org/x/hQIuCg</a><span style="color:black">) and the staff support team has already pulled together an index of relevant resources (see
</span><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1UsNgPAVavQ0b257LVquHxPTZ7IPnp6fr/edit__;!!PtGJab4!u5NwC2cny3f54eyaS5KogdELkowtqrc57gWQt0SEMd4ZGCZTcXc90_284soTrl_vi5NB6yfk-w$" target="_blank"><span style="color:#0052CC;background:white">https://docs.google.com/document/d/1UsNgPAVavQ0b257LVquHxPTZ7IPnp6fr/edit#</span>
[docs.google.com]</a><span style="color:black">). It is key that you familiarize yourself with these documents as well as the instructions provided by the GNSO Council to this team (see
</span><a href="https://community.icann.org/x/QoFaCg" target="_blank">https://community.icann.org/x/QoFaCg</a><span style="color:black">). </span><o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">We have an incredible ICANN policy support team in Marika, Barry, Caitlin, Terry and others and I believe you will see that in the preparatory materials that they have prepared. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US">Our first meeting will be on <b><u><span style="color:black">Tuesday 5 October at 14.00 UTC</span></u></b><span style="color:black"> for which you will receive a calendar invite shortly. In addition to introductions
and sharing of expectations, I also plan to start a conversation on how to best organize and plan our work as our first order of business will be to develop a work plan. To support this conversation, the staff support team is working on a set of background
briefings for each assignment that will be shared shortly. I am a big fan of using an agile approach so I would like the team to consider limiting the number of plenary sessions and trying to get some of the work done using small teams. But of course, a decision
on this will be in your hands.</span><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black">I look forward to working with all of you and please look out for further communications ahead of our first meeting. </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black">Best regards, </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="margin:0cm"><span lang="EN-US" style="color:black">Michael Palage</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
GNSO-Accuracy-ST mailing list<br>
<a href="mailto:GNSO-Accuracy-ST@icann.org" target="_blank">GNSO-Accuracy-ST@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-accuracy-st" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-accuracy-st</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://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</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.<o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>