<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)"><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:blue;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-compose;
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 style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hello All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I reached out to Brian Beckham from WIPO in response to this thread yesterday. Listed below is his email response. I also spoke with Brian today about how we might go about involving other UDRP providers in this outreach. If we complete our assignments tomorrow we can add this to the agenda.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michael<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><EMAIL RESPONSE FROM BRIAN BECKHAM (WIPO)> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Thanks Michael,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Do let me know if/how we can assist.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>An initial observation, which you and the WG will already know, is that while perhaps anecdotally useful, this will yield incomplete data and obviously the search terms should be creatively widened (yet will inevitably not be fully comprehensive given that if a panel chooses to record such fact in the decision, it could do so in different ways (or even in different places: e.g., in the procedural history vs the bad faith analysis) and using different terms).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>If only to state the obvious, information can be “accurate” in the sense that it provides an entry into the required data fields, but still inaccurate in the sense of authenticity vis-à-vis an actual registrant. These types of scenarios in particular cause unnecessary time (giving room for cyberflight, or prolonged illegitimate activity) and expense in the UDRP cases, and even potential due process issues (even if they would be occasioned by registrants). While this goes beyond UDRP cases (as will your efforts), I wonder if your WG has considered the utility of cross-field challenge/matching (which may not be the technical term) such as is employed by postal and shipping companies around the world (i.e., you cannot provide a 4-digit zip code in Switzerland but list a US or UK address).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Mindful that these conversations and policies need to look at scale and potential ripple effects/unintended consequences, I would also caution, as Roger seems to allude to below, that there may indeed be broader policy considerations than a mere one-to-one correlation between “extent” and “impact” can reasonably be expected to reveal.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>While a slightly different topic (P/P), the following may be of interest: <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><a href="https://circleid.com/posts/20201104-icann-meeting-concluded-with-no-action-on-dns-abuse-or-privacy">https://circleid.com/posts/20201104-icann-meeting-concluded-with-no-action-on-dns-abuse-or-privacy</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Thanks, and again, do let me know if we can assist further.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Brian <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>