<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    It would be inappropriate to presume cybersquatting from the use of
    a "well known" brand name alone. There are any number of legitimate
    reasons for registering <brand>.<new gTLD>. And we have
    no working standard for what "well known" means, especially
    internationally. Cybersquatting requires intent, and if some
    percentage of URS proceedings are presuming intent based on no facts
    but the domain name itself, that's highly relevant information that
    should not be buried here.<br>
    <pre class="moz-signature" cols="72">Mitch Stoltz
Senior Staff Attorney, EFF | 415-436-9333 x142
<a class="moz-txt-link-freetext" href="https://www.eff.org/donate">https://www.eff.org/donate</a> | <a class="moz-txt-link-freetext" href="https://act.eff.org/">https://act.eff.org/</a> 
</pre>
    <div class="moz-cite-prefix">On 2/10/20 11:53 AM, <a class="moz-txt-link-abbreviated" href="mailto:cking@modernip.com">cking@modernip.com</a>
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:046d01d5e04b$beaaeee0$3c00cca0$@modernip.com">
      <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:"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:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Century Gothic";
        panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Century Gothic",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;}
/* List Definitions */
@list l0
        {mso-list-id:118300815;
        mso-list-template-ids:1946825960;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:186988836;
        mso-list-template-ids:-777463626;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2
        {mso-list-id:286475992;
        mso-list-template-ids:745937178;}
@list l2:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3
        {mso-list-id:663435329;
        mso-list-template-ids:-1876283272;}
@list l3:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4
        {mso-list-id:954561835;
        mso-list-template-ids:1678007804;}
@list l4:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l4:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5
        {mso-list-id:1197741644;
        mso-list-template-ids:1319772622;}
@list l5:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l5:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6
        {mso-list-id:1281571870;
        mso-list-template-ids:181028222;}
@list l6:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l6:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7
        {mso-list-id:1672219279;
        mso-list-template-ids:-1569800282;}
@list l7:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l7:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8
        {mso-list-id:1687756206;
        mso-list-template-ids:-1351703236;}
@list l8:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l8:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9
        {mso-list-id:1797984224;
        mso-list-template-ids:-1820325450;}
@list l9:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l9:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10
        {mso-list-id:1978872088;
        mso-list-template-ids:1089364718;}
@list l10:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l10:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11
        {mso-list-id:2042590061;
        mso-list-template-ids:-446286078;}
@list l11:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l11:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12
        {mso-list-id:2084444324;
        mso-list-template-ids:-177955002;}
@list l12:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l12:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:"Century
            Gothic",sans-serif">Agree Georges.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:"Century
            Gothic",sans-serif">We don’t need a percent figure.  We
            can simply observe that ICANN needs specific info for data
            collection/oversight & outline those required fields.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:"Century
            Gothic",sans-serif"><o:p> </o:p></span></p>
        <div>
          <p class="MsoNormal"><b><span style="font-family:"Century
                Gothic",sans-serif;color:#0D0D0D"><o:p> </o:p></span></b></p>
          <p class="MsoNormal"><b><span style="font-family:"Century
                Gothic",sans-serif;color:#0D0D0D">Cyntia King<o:p></o:p></span></b></p>
          <p class="MsoNormal"><span
              style="font-size:11.0pt;font-family:"Century
              Gothic",sans-serif;color:#0D0D0D">O:  +1 816.633.7647<o:p></o:p></span></p>
          <p class="MsoNormal"><span
              style="font-size:11.0pt;font-family:"Century
              Gothic",sans-serif;color:#0D0D0D">C:  +1 818.209.6088<o:p></o:p></span></p>
          <p class="MsoNormal"><span
              style="font-size:11.0pt;font-family:"Century
              Gothic",sans-serif;color:#0D0D0D"><img
                style="width:1.3437in;height:.6041in"
                id="Picture_x0020_1"
                src="cid:part1.EABEE48C.920153F5@eff.org" alt="Email
                Logo5" class="" width="129" height="58"><o:p></o:p></span></p>
        </div>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:"Century
            Gothic",sans-serif"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
                  style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
                GNSO-RPM-WG <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rpm-wg-bounces@icann.org"><gnso-rpm-wg-bounces@icann.org></a> <b>On
                  Behalf Of </b>Nahitchevansky, Georges<br>
                <b>Sent:</b> Monday, February 10, 2020 1:37 PM<br>
                <b>To:</b> Greg Shatan <a class="moz-txt-link-rfc2396E" href="mailto:gregshatanipc@gmail.com"><gregshatanipc@gmail.com></a>;
                gnso-rpm-wg <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rpm-wg@icann.org"><gnso-rpm-wg@icann.org></a><br>
                <b>Subject:</b> Re: [GNSO-RPM-WG] The 7% Solution for
                URS Rationale [was: ACTIONS & NOTES: RPM PDP WG 08
                August 2018]<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank
            you Greg.  I was looking for that email and went back
            through what I had reviewed.  The bottom line is that of the
            103 cases that had been marked as having no rational, there
            were 45 that included enough to know what the case had been
            about and the rationale.  That meant that 7% just reiterated
            the standard and ruled in favor of a party with nothing to
            deduce the rationale.  Of those 7%, though, a number of
            cases involved domain names that were based on a well-known
            trademark and it would not take much to understand that a
            domain name that was simply BRAND + gTLD likely involved
            cybersquatting.  So in my view while there are some cases
            that had no rationale, I do not believe we are talking
            overall about cases that involved rulings with no
            explanations regarding domain names that primarily involved
            a generic word with a gTLD.  Most of the 58 cases (or 103)
            that arguably had no specific rationale involved domain
            names that related to trademarks that are known, which again
            suggests something about the ruling.  Put another way, there
            is a conceptual difference between a case that involves a
            domain name based on a well-known brand such as
            <cocacola.beverage> and one that involves a generic
            word such as <fashion.clothes>.  If the cases that
            have no articulated rationale primarily involved the latter
            type of domains, I would be much more concerned.  But if
            they mostly relate to known brands, I’m not sure that this
            suggests that there were errors committed by the panelist. 
            Also, I do not believe that the 58 decisions at issue
            actually resulted in any appeals, which does suggest that
            perhaps the decisions were not unfounded.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">In
            any event, rather than go back and forth about whether we
            are talking about 7% or 13% of cases without a stated
            rationale, I think the solution is to just say that there
            were several cases that had no clearly stated rationale
            without getting into percentages. After all, we are more or
            less in agreement that close to 90% of the cases had
            articulated rationale and that there should be some tweak to
            address the minimum of what a URS decision should provide. <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Georges
            Nahitchevansky       </span><span style="color:#1F497D"> </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoNormal"><b><span
              style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
            GNSO-RPM-WG <<a
              href="mailto:gnso-rpm-wg-bounces@icann.org"
              moz-do-not-send="true">gnso-rpm-wg-bounces@icann.org</a>>
            <b>On Behalf Of </b>Greg Shatan<br>
            <b>Sent:</b> Monday, February 10, 2020 1:42 PM<br>
            <b>To:</b> gnso-rpm-wg <<a
              href="mailto:gnso-rpm-wg@icann.org" moz-do-not-send="true">gnso-rpm-wg@icann.org</a>><br>
            <b>Subject:</b> [GNSO-RPM-WG] The 7% Solution for URS
            Rationale [was: ACTIONS & NOTES: RPM PDP WG 08 August
            2018]<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><br>
           <o:p></o:p></p>
        <div>
          <div>
            <p class="MsoNormal"><span
                style="font-family:"Verdana",sans-serif">All,<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
                style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
                style="font-family:"Verdana",sans-serif">Here
                is the Georges Nahitchevansky email that was referred to
                in last week's discussion of the percentage of URS
                decisions that lacked a rationale.  There was a
                subsequent discussion, so I recommend going back to the
                list if you want to see the follow-up.<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
                style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
                style="font-family:"Verdana",sans-serif">Greg<o:p></o:p></span></p>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <div>
              <p class="MsoNormal">---------- Forwarded message
                ---------<br>
                From: <strong>Nahitchevansky, Georges</strong> <<a
                  href="mailto:ghn@kilpatricktownsend.com"
                  target="_blank" moz-do-not-send="true">ghn@kilpatricktownsend.com</a>><br>
                Date: Thu, Aug 9, 2018 at 3:27 PM<br>
                Subject: Re: [gnso-rpm-wg] ACTIONS & NOTES: RPM PDP
                WG 08 August 2018<br>
                To: Tushnet, Rebecca <<a
                  href="mailto:rtushnet@law.harvard.edu" target="_blank"
                  moz-do-not-send="true">rtushnet@law.harvard.edu</a>>,
                Ariel Liang <<a href="mailto:ariel.liang@icann.org"
                  target="_blank" moz-do-not-send="true">ariel.liang@icann.org</a>>,
                <a href="mailto:gnso-rpm-wg@icann.org" target="_blank"
                  moz-do-not-send="true">gnso-rpm-wg@icann.org</a> <<a
                  href="mailto:gnso-rpm-wg@icann.org" target="_blank"
                  moz-do-not-send="true">gnso-rpm-wg@icann.org</a>><o:p></o:p></p>
            </div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
            <div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Rebecca:</span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I
                    do not disagree with the notion that we should
                    discuss what a decision should contain, but I don’t
                    think we have a consensus as to what that should be
                    in the URS context (given the pricing of URS
                    proceedings).  Moreover, a review of the URS cases
                    makes your 13% number and comment of “significant
                    due process and implementation issues” point
                    questionable.  At NAF for example, there were 827
                    cases that that your research assistants reviewed. 
                    I found a total of about 103 that your team flagged
                    as having no articulated decisions.  I would agree
                    that in 58 cases the decisions lacked details, but
                    in 45 cases there were details that sufficiently let
                    you know what the case was about and the basis of
                    the resolution.  I am sure we can argue about these
                    45 cases and whether they should say more, but
                    ultimately we are really only talking about 58 cases
                    that actually do not have any specific details and
                    just provide the standard and a resolution (although
                    I note that most of these cases involve domain names
                    based on fairly well known marks such as NISSAN,
                    DATSUN, TEXACO, BLOOMBERG, BNP PARIBAS etc., so you
                    pretty much know what trademark was involved.).  In
                    all, we are really talking about 7% of the cases
                    that have no details, which is not significant.</span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Again,
                    we can discuss what the decisions should provide,
                    but I don’t think we ought to be qualifying this as
                    a “significant” issue per se (as 93% of them have
                    details).  There are other issues being considered
                    in the URS review that have better percentage
                    numbers as an issue that are viewed as not being
                    significant per se. The point is that the URS looks
                    to be working appropriately and there are probably
                    some tweaks and refinements needed but this is not
                    sky is falling issue.</span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
                <div>
                  <div style="border:none;border-top:solid #E1E1E1
                    1.0pt;padding:3.0pt 0in 0in 0in">
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
                        gnso-rpm-wg <<a
                          href="mailto:gnso-rpm-wg-bounces@icann.org"
                          target="_blank" moz-do-not-send="true">gnso-rpm-wg-bounces@icann.org</a>>
                        <b>On Behalf Of </b>Tushnet, Rebecca<br>
                        <b>Sent:</b> Thursday, August 9, 2018 1:22 PM<br>
                        <b>To:</b> Ariel Liang <<a
                          href="mailto:ariel.liang@icann.org"
                          target="_blank" moz-do-not-send="true">ariel.liang@icann.org</a>>;
                        <a href="mailto:gnso-rpm-wg@icann.org"
                          target="_blank" moz-do-not-send="true">gnso-rpm-wg@icann.org</a><br>
                        <b>Subject:</b> Re: [gnso-rpm-wg] ACTIONS &
                        NOTES: RPM PDP WG 08 August 2018</span><o:p></o:p></p>
                  </div>
                </div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <div
                  id="m_-6589448025614526953m_-1652018880868742861divtagdefaultwrapper">
                  <p><span
                      style="font-family:"Calibri",sans-serif;color:black">My
                      apologies for missing the meeting.  Comment on the
                      big document:</span><o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Calibri",sans-serif;color:black">This is
                      currently only covered under Defenses but I would
                      put it for discussion/recommendations under 2.
                      Examiners’ Guide/3. Other Issues because it goes
                      beyond defenses: Decisions should contain basic
                      information, including what the trademark is, what
                      the finding of abuse is and/or what findings are
                      on any defenses—13% of decisions did not, and this
                      raises significant due process and implementation
                      issues.  </span><o:p></o:p></p>
                </div>
                <div class="MsoNormal" style="text-align:center"
                  align="center">
                  <hr width="98%" size="2" align="center"></div>
                <div
                  id="m_-6589448025614526953m_-1652018880868742861divRplyFwdMsg">
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
                      gnso-rpm-wg <<a
                        href="mailto:gnso-rpm-wg-bounces@icann.org"
                        target="_blank" moz-do-not-send="true">gnso-rpm-wg-bounces@icann.org</a>>
                      on behalf of Ariel Liang <<a
                        href="mailto:ariel.liang@icann.org"
                        target="_blank" moz-do-not-send="true">ariel.liang@icann.org</a>><br>
                      <b>Sent:</b> Wednesday, August 8, 2018 3:56:54 PM<br>
                      <b>To:</b> <a href="mailto:gnso-rpm-wg@icann.org"
                        target="_blank" moz-do-not-send="true">gnso-rpm-wg@icann.org</a><br>
                      <b>Subject:</b> [gnso-rpm-wg] ACTIONS & NOTES:
                      RPM PDP WG 08 August 2018</span> <o:p></o:p></p>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  </div>
                </div>
                <div>
                  <div>
                    <p><span style="font-size:11.0pt;color:black">Dear
                        All,</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black"> </span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">Please see
                        below the action items and notes captured by
                        staff from the RPM PDP WG call held on
                        08 August 2018 (17:00-18:30 UTC). Staff have
                        posted to the wiki space the action items and
                        notes.  <i>Please note that these will be
                          high-level notes and are not meant as a
                          substitute for the recording.</i> The
                        recording, AC chat, and attendance records are
                        posted on the wiki at: <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_uwNpBQ&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=CypdnKxuYaImNW0ttGO-h5FbHiLxMQ2kzt4bzMuwnHU&s=gcgRms-bmezGQQmwXCqLMQXOdSv3gly_0bWYNSuRlY8&e="
                          target="_blank" moz-do-not-send="true">https://community.icann.org/x/uwNpBQ</a>
                      </span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">    </span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">Best
                        Regards,</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">Ariel</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black"> </span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">Ariel
                        Xinyue Liang</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">GNSO Policy
                        Support Specialist</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><span
                        style="font-size:11.0pt;color:black">Internet
                        Corporation for Assigned Names and Numbers
                        (ICANN)</span><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><b><span
                          style="font-size:11.0pt;color:black"> </span></b><o:p></o:p></p>
                    <p style="text-align:start;word-spacing:0px"><b><span
                          style="font-size:11.0pt;color:black">==</span></b><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION
                          ITEMS:</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                        level1 lfo1"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Brian
                          Beckham to send to the WG a WIPO FAQ with
                          regard to “Doe Complaint”.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                        level1 lfo1"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Renee
                          Fossen to provide more information on
                          HSTS-preloaded domain suspension issues in the
                          written responses.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                        level1 lfo1"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Staff
                          to recirculate the Super Consolidated URS
                          Topics Table document</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                        level1 lfo1"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">WG
                          members to provide substantive comment and
                          raise anything they believe is missing on the
                          WG mailing list by <b>COB Tue, 14 Aug</b>.
                          Co-Chairs will then discuss among themselves
                          to determine further actions/process. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                        level1 lfo1"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">WG
                          members to finish reviewing the rest of the
                          Super Consolidated URS Topics Table document,
                          including page 24-35, during next week’s call.
                          Later period to discuss larger policy issues. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">NOTES:</span></b><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Review
                          Agenda/Statements of Interest</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l11
                        level1 lfo2"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">George
                          Kirikos has become a member of the At-Large
                          Community: <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_gnsosoi_George-2BKirikos-2BSOI&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=CypdnKxuYaImNW0ttGO-h5FbHiLxMQ2kzt4bzMuwnHU&s=8-YfNNseZ7YW77BHJT9ciEr_I08JQcazWKn1rxNI900&e="
                            target="_blank" moz-do-not-send="true">https://community.icann.org/display/gnsosoi/George+Kirikos+SOI</a>
                        </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">General
                          Comment on the Super Consolidated URS Topics
                          Table Document </span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
                          topics in the table were developed by the WG
                          members and deliberated on by the WG & URS
                          Sub Teams. Each Sub Team then did very
                          substantial work on data collection and
                          reviewing what came back. While the actual Sub
                          Team recommendations and suggestions captured
                          in this document are what is intended the WG
                          should discuss - to see if it wishes to
                          develop policy or operational recommendations
                          - discussion over what should be on the actual
                          list of topics should not be reopened unless
                          the WG agrees to do so. We encourage all WG
                          members to review all the previous reports
                          from each Sub Team, and all the documents they
                          worked on. They are linked in this Super
                          Consolidated document (page 2).</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
                          Super Consolidated document is a summary of
                          findings and suggestions by the Sub Teams. The
                          Table does not mean to limit/restrict
                          recommendations from the WG members. If there
                          is any issue overlapping with UDRP, can
                          possibly be carried over to the phase II of
                          the PDP. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is
                          it possible to add additional topics to the
                          Super Consolidated Table? One WG member said
                          that access to the Courts, for example, is a
                          topic he raised, which isn't in the table.
                          Statute of Limitations, whether URS should
                          apply to legacy gTLDs as a consensus policy,
                          are just a few of the topics not in the table.
                          He brought it up in November 2017 (see: <a
href="https://mm.icann.org/pipermail/gnso-rpm-wg/2017-November/002585.html"
                            target="_blank" moz-do-not-send="true">https://mm.icann.org/pipermail/gnso-rpm-wg/2017-November/002585.html</a>
                          ) and it was reflected in a later document.
                          That's a critical issue for registrants. if
                          they don't have access to the courts to
                          challenge a URS decision, then it's a huge
                          denial of their rights.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">While
                          the chart is not meant to foreclose further
                          discussion, it is a good faith attempt at
                          capturing the work of the sub teams.  The
                          purpose of today's, and likely the next few,
                          calls was to make sure this was an accurate
                          and comprehensive reflection of our
                          discussions so far.  That said, WG members
                          should bear in mind that we are seeking
                          consensus, so items which are unlikely to
                          achieve that may not be appropriate to reflect
                          as a recommendation, but could be included in
                          public comments on the Initial Report.  Also,
                          before adding items to this chart, we will
                          want to work with staff to see whether such
                          topics was previously discussed, and if so,
                          the level of agreement/consensus.  In other
                          words, it is not necessary final, but is
                          equally an opportunity to reintroduce topics
                          which have been discussed, but for which
                          consensus is/was not possible.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could
                          we create a list of "missing issues" -- a list
                          of issues raised in this call (and calls to
                          follow); we can evaluate the nature and weight
                          of these ideas later.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l7
                        level1 lfo3"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regarding
                          the Action Items highlighted in column 3 of
                          the table, Providers ST will do a first pass
                          of the responses from the Providers to the
                          follow-up questions, and then discuss the
                          issues that they identified and proposed
                          suggestions with the full WG. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Limited
                          filing period (page 3) </span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8
                        level1 lfo4"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          WG member believes that there should be
                          limitation for filing period to bring URS
                          Complaints, so the domain registered many
                          years ago would not be subject to unfair
                          treatment. He said a registrant who owns a
                          domain for 20 years, for example, shouldn't
                          have to be concerned about a policy that can
                          take their domain down with very short time
                          period to respond.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8
                        level1 lfo4"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Other
                          WG members said this was discussed, and did
                          not achieve agreement. That would only even be
                          an option if the trademark pre-dated. This is
                          unlikely to be a situation in practice where a
                          URS was brought because it would probably not
                          be a "slam dunk" case after 20 years unless
                          there had been a change of circumstances. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8
                        level1 lfo4"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">On
                          the issue of delay and laches - as reported by
                          the Docs Sub Team, the data did not provide
                          any basis for which a policy recommendation
                          should be made. The Providers and
                          Practitioners Sub Teams also did not uncover
                          any specific issues that came to either
                          practitioners' or providers' attention.</span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Administrative
                          Review (page 3-4) </span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5
                        level1 lfo5"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          WG member asked whether ICANN should bring
                          Providers into contractual relationship in
                          order to enforce the URS Rules &
                          Procedures. Another member said it probably
                          need to be ICANN’s legal department to enforce
                          the rules & procedure. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5
                        level1 lfo5"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">URS
                          Providers have MoU with ICANN. Whether it is
                          ICANN’s compliance department or legal
                          department to enforce the rules &
                          procedures, it should not be controversial
                          that Providers must abide by them. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5
                        level1 lfo5"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">An
                          MOU could be legally enforceable, depending on
                          the circumstances. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">500-word
                          Complaint limit (page 4-5)</span></b><o:p></o:p></p>
                    <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.45pt"><span
                        style="font-size:10.0pt;font-family:Symbol">·</span><span
                        style="font-size:7.0pt">        </span><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif">On
                        500-word Complaint Limit - Practitioners' survey
                        results were split (out of 12, 5 agree it's
                        sufficient, 4 disagree); results included
                        feedback from some that the word limit was too
                        low: "arbitrary and often insufficient" and
                        "should be slightly increased".</span><o:p></o:p></p>
                    <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.45pt"><span
                        style="font-size:10.0pt;font-family:Symbol">·</span><span
                        style="font-size:7.0pt">        </span><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                        member said he understands and generally agrees
                        with the decision not to suggest an expansion of
                        the word limit, he wonders if there aren't
                        situations (multi- domain challenges, etc.)
                        where a Complainant or Respondent might be given
                        the opportunity to request an expansion. This
                        point can be captured for decisional phase.</span><o:p></o:p></p>
                    <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.45pt"><span
                        style="font-size:10.0pt;font-family:Symbol">·</span><span
                        style="font-size:7.0pt">        </span><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif">Another
                        member suggested that perhaps providers can
                        provide stats on the average word length of
                        complaints, to see how close to the 500 words
                        they are at present. (i.e. a table of
                        distributions, e.g. 10% under 200 words, 20%
                        between 201 and 300, etc.)</span><o:p></o:p></p>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Amending
                          the Complaint in light of GDPR/Temp Spec (page
                          5-6)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
                        level1 lfo6"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          member believes that 2-3 days might not be a
                          good rule (e.g. weekends, time to research,
                          etc.). Maybe 5 business days.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
                        level1 lfo6"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">WIPO’s
                          approach to “doe complaints” has been very
                          helpful and provides some comfort that the
                          lack of true registrant/registrant
                          organization data masked due to GDPR will not
                          result in a deficient complaint for an omitted
                          respondent.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
                        level1 lfo6"><b><span
                            style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION
                            ITEM: </span></b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Brian
                          Beckham to send to the WG a WIPO FAQ with
                          regard to “Doe Complaint”.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
                        level1 lfo6"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Forum
                          is asking for amendment of the complaint in
                          UDRP - under the rules that's not allowed in
                          URS.</span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">SMD
                          Files (page 6-7)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">SMD
                          files are used for limited purpose of
                          demonstrating the use. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Recollection
                          is that SMD files would be passed to the
                          Examiners and relay the critical information
                          related to the TM registration. That's why
                          some people are surprised by the limited info
                          SMD files would provide. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
                          SMD files contain some basic human-readable
                          information, with the rest of the information
                          coded. For example, the trademark itself is
                          human-readable but the applicable Nice
                          classification is coded. A SMD file is used by
                          registries/registrars for validation, and as
                          Greg noted, to demonstrate use. From the TMCH
                          provider: <a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.trademark-2Dclearinghouse.com_help_faq_which-2Dinformation-2Ddoes-2Dsmd-2Dfile-2Dcontain&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=CypdnKxuYaImNW0ttGO-h5FbHiLxMQ2kzt4bzMuwnHU&s=v3df_qE8Dw_U7YY7_IfhIMgGSxt-a44LbNskorrbTIg&e="
                            target="_blank" moz-do-not-send="true">http://www.trademark-clearinghouse.com/help/faq/which-information-does-smd-file-contain</a>
                            </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">If
                          the intent of the STI was that the SMD file
                          would be a file summary, that got lost
                          somewhere along the way, way before the SMD
                          file was designed by the TMCH providers.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Rules
                          3(b)(v) Specify the trademark(s) or service
                          mark(s) on which the complaint is based and
                          the goods or services with which the mark is
                          used including evidence of use –which can be a
                          declaration and a specimen of current use in
                          commerce - submitted directly or by including
                          a relevant SMD (Signed Mark Data) from the
                          Trademark Clearinghouse</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">It
                          might be useful to look at the spec that they
                          relied on.  But the real question is how
                          should the examiner get the relevant data
                          about the Complainant’s mark. The SMD file is
                          probably not the answer, if it was ever
                          intended to be.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
                        level1 lfo7"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">the
                          Examiner is not required to second-guess the
                          SMD file. Its existence is sufficient that the
                          mark has had use validated by the TMCH.</span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Other
                          Topics (page 7-8)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l12
                        level1 lfo8"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">These
                          are policy proposals can be brought up when WG
                          members are proposing changes to the URS
                          policy itself. Charter asks us to address the
                          question whether the URS should become a
                          consensus policy applicable to legacy domains.
                          Charter is not specific regarding whether such
                          discussion should occur in phase I or phase
                          II. This feedback illustrates that the ST
                          didn't get to propose policy changes, it is
                          for the WG to discuss and propose changes. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l12
                        level1 lfo8"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">when
                          we reference the STI and IRT reports, we need
                          to keep in mind they only had about 1-2 months
                          to complete their work and produce a report;
                          they were not standard PDP working groups and
                          had limited charters and mandates, which were
                          set by the Board</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l12
                        level1 lfo8"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">This
                          is feedback from one Provider, who may want to
                          grow their business. Practitioners survey are
                          from Complaints' side. Need to have a balanced
                          solution when considering the input. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l12
                        level1 lfo8"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">There
                          were plenty of practitioners that represent
                          registrants in the Subgroup, although their
                          experience was largely with the UDRP.</span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Duration
                          of response period (Page 11)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9
                        level1 lfo9"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          member believes that if the URS continues in
                          its current form, it would affect valuable
                          domain names. The ones the registrants that do
                          want to defend them, 14 days are not
                          sufficient. 20 days may be more appropriate.
                          It should be based on the age of the domain
                          name. If a domain is 3 months, it will have a
                          shorter period to respond. If you own a domain
                          name for 5-10 years, response period would be
                          longer so less urgency. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9
                        level1 lfo9"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Several
                          other WG members disagree. The URS is supposed
                          to be an expedited proceeding so increasing
                          the length of time of a streamlined proceeding
                          defeats the purpose.  At most, there could be
                          an additional 3 or 4 days extension period for
                          cause. The point is that there are enough
                          circumstances that give rise to the URS 'quick
                          response' that we should NOT make assumptions
                          into policy.  It is an assumption that an
                          "aged" domain would not require a fast
                          response. In Mexico, we have not been able to
                          file a domain name case due to Courts
                          ignorance about the subject and also, because
                          it could take years to be solved. We're
                          spinning out fo control - extending the time
                          to respond to URS cases just because a domain
                          registration is not new defeats the purpose of
                          fast action to take down an infringing domain
                          once it's discovered. The URS is meant to
                          address clear and convincing cases of
                          infringement. A person registers a domain name
                          for less than $50 and brand owner find out
                          about at some point and then files an
                          injunction in court for tens of thousands of
                          dollars.  Where is the balance. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Examiners
                          Guide (page 13) </span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l10
                        level1 lfo10"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
                          WIPO guidance for examiners took 1500 hours to
                          develop. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l10
                        level1 lfo10"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
                          WIPO guidance is relevant to the URS, the
                          elements are shown are the same and the
                          differences include the burden of proof, word
                          limit, etc. A lot of WIPO guidance goes to the
                          shade of grey issues. URS is for clear
                          black/white cases, so if there is a URS
                          guidance it would likely be abbreviated. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Duration
                          of Suspension Period & Review of
                          Implementation (page 21-23)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6
                        level1 lfo11"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          WG member suggests to find out how much cost
                          for registries & registrars to comply with
                          the URS rules and procedures. Need to get
                          data/feedback from the registries/registrars. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6
                        level1 lfo11"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Other
                          WG members are not sure "cost of
                          implementation of URS" for
                          Registries/Registrars is relevant to
                          effectiveness of URS. We don't need to do a
                          cost/benefit analysis (the costs &
                          benefits aren't ICANN's), the providers,
                          registrars, registries need to be asked if
                          they are overburdened by the costs of
                          compliance.</span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6
                        level1 lfo11"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">There
                          is an action item to contact the
                          registries/registrars about these issues.
                          Timing TBD due to Sunrise & Claims survey
                          launch. </span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">Other
                          topics (page 23-24)</span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
                        level1 lfo12"><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">One
                          WG member thinks the HSTS issue is not
                          difficult to fix. The Providers need to
                          improve their technical applicability to
                          resolve the issue. Renee Fossen from Forum
                          disagrees. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
                        level1 lfo12"><b><span
                            style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION
                            ITEM</span></b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
                          Renee Fossen to provide more information on
                          HSTS-preloaded domain suspension issues in the
                          written responses.</span><o:p></o:p></li>
                    </ul>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><span
                        style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
                    <p><b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">NEXT
                          STEPS </span></b><o:p></o:p></p>
                    <ul type="disc">
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
                        level1 lfo13"><b><span
                            style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION
                            ITEM</span></b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
                          Staff to recirculate the Super Consolidated
                          URS Topics Table document and ask all WG
                          members to provide substantive comment and
                          raise anything they believe is missing on the
                          WG mailing list by COB Tue, 14 Aug. Co-Chairs
                          will then discuss among themselves to
                          determine further actions/process. </span><o:p></o:p></li>
                      <li class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
                        level1 lfo13"><b><span
                            style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION
                            ITEM</span></b><span
                          style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
                          WG to finish reviewing the rest of the Super
                          Consolidated URS Topics Table document,
                          including page 24-35. Later period to discuss
                          larger policy issues. </span><o:p></o:p></li>
                    </ul>
                    <p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
                  </div>
                </div>
              </div>
              <p class="MsoNormal"><o:p> </o:p></p>
              <div class="MsoNormal" style="text-align:center"
                align="center">
                <hr width="100%" size="2" align="center"></div>
              <p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black"><br>
                  Confidentiality Notice:<br>
                  This communication constitutes an electronic
                  communication within the meaning of the Electronic
                  Communications Privacy Act, 18 U.S.C. Section 2510,
                  and its disclosure is strictly limited to the
                  recipient intended by the sender of this message. This
                  transmission, and any attachments, may contain
                  confidential attorney-client privileged information
                  and attorney work product. If you are not the intended
                  recipient, any disclosure, copying, distribution or
                  use of any of the information contained in or attached
                  to this transmission is STRICTLY PROHIBITED. Please
                  contact us immediately by return e-mail or at 404 815
                  6500, and destroy the original transmission and its
                  attachments without reading or saving in any manner.</span><o:p></o:p></p>
              <div class="MsoNormal" style="text-align:center"
                align="center">
                <hr width="100%" size="2" align="center"></div>
              <p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black"><br>
                  ***DISCLAIMER*** Per Treasury Department Circular 230:
                  Any U.S. federal tax advice contained in this
                  communication (including any attachments) is not
                  intended or written to be used, and cannot be used,
                  for the purpose of (i) avoiding penalties under the
                  Internal Revenue Code or (ii) promoting, marketing or
                  recommending to another party any transaction or
                  matter addressed herein.</span><o:p></o:p></p>
            </div>
            <p class="MsoNormal">_______________________________________________<br>
              gnso-rpm-wg mailing list<br>
              <a href="mailto:gnso-rpm-wg@icann.org" target="_blank"
                moz-do-not-send="true">gnso-rpm-wg@icann.org</a><br>
              <a
                href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg"
                target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><o:p></o:p></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
GNSO-RPM-WG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GNSO-RPM-WG@icann.org">GNSO-RPM-WG@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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.</pre>
    </blockquote>
    <br>
  </body>
</html>