<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.null, li.null, div.null
{mso-style-name:null;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
.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:199052628;
mso-list-template-ids:-1087592970;}
@list l0:level1
{mso-level-start-at:7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:347371449;
mso-list-template-ids:-2046511062;}
@list l1:level1
{mso-level-start-at:8;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:511721691;
mso-list-template-ids:-1308843208;}
@list l2:level1
{mso-level-start-at:8;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:568809445;
mso-list-template-ids:1728736164;}
@list l3:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:705181302;
mso-list-template-ids:12061760;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:\F0B7;
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:757336888;
mso-list-template-ids:1002322832;}
@list l6
{mso-list-id:872577586;
mso-list-template-ids:611582218;}
@list l6:level1
{mso-level-start-at:6;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7
{mso-list-id:887230701;
mso-list-template-ids:204916112;}
@list l7:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8
{mso-list-id:1511140312;
mso-list-template-ids:-1952052662;}
@list l8:level1
{mso-level-start-at:9;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9
{mso-list-id:1570922563;
mso-list-template-ids:1591748356;}
@list l9:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10
{mso-list-id:1750152772;
mso-list-template-ids:827257060;}
@list l10:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11
{mso-list-id:1771970827;
mso-list-template-ids:-1310306916;}
@list l11:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l12
{mso-list-id:1975484257;
mso-list-template-ids:437811570;}
@list l12:level1
{mso-level-start-at:6;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Phil, all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">I have noted a number of exchanges in this thread, including those by Jeff Neuman and others raising the need for sending such a letter. Without wishing to weigh in on the
decision to send a letter or not, <b><i>if a letter is sent, I propose the edits in the attached (it is easier to read in “final”)</i></b>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(I hope this is ok, and I suppose the document permissions were inadvertently tagged as “This document has been marked as final to discourage editing.” ; )<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">As to the chart, on the UDRP side, it should include:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 2
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 4(b)(i) – (iv)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 4(c)(i) – (iii)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 4(f)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 7<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP para 8(a)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- the full text of UDRP Rules para 2 (i.e., not skipping the obligations preamble)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP Rules para 4(b)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- UDRP Rules para 17 (a)(i) – (vii)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">If the reference to UDRP Rules para 6(a) and (d) are retained, UDRP Rules para 6(c) and (f) should be added. I also suggest removing the term “PII” from both the chart title
and the legend.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Brian
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-rpm-wg [mailto:gnso-rpm-wg-bounces@icann.org]
<b>On Behalf Of </b>Corwin, Philip via gnso-rpm-wg<br>
<b>Sent:</b> Thursday, April 26, 2018 9:58 PM<br>
<b>To:</b> gnso-rpm-wg@icann.org<br>
<b>Subject:</b> [gnso-rpm-wg] Draft Letter on UDRP & URS Utilization of WHOIS-Derived Registrant Data (was Response from the Co-Chairs RE: Proposal to Shift URS review to Phase II)<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose">WG members:<o:p></o:p></a></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Following up on the co-chairs email of April 6<sup>th</sup>, in which we stated--<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:2.25pt">In regard to the ability of URS and UDRP providers to continue to have access to the data elements necessary to fulfill their dispute resolution provider (DRP) roles, it is our intent to prepare
a draft letter to ICANN’s CEO noting that such continued access for DRPs is essential to maintaining these non-judicial alternatives for addressing trademark infringement in the DNS, and requesting that ICANN raise this important matter in its continuing discussions
with EU Data Protection Authorities. We will work with staff to prepare this draft letter and then share it with WG members for review and comment, after which we will coordinate with Council Leadership and the WG Liaison regarding transmission of a final
text to ICANN management. –<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:2.25pt"><o:p> </o:p></p>
<p class="MsoNormal">Kathy and I have now prepared a draft letter to the GNSO Council, for transmission onward to ICANN management and other parties, for your review. It addresses the subject of the relationship of UDRP and URS administration based upon registrant
data obtained from WHOIS records. In preparing this letter we relied extensively on the attached listing of UDRP Policy and Rules and URS Rules and Procedure that mention or are related to registrant data and WHOIS.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please review this attached letter at your earliest opportunity and post any suggested revisions or additions to the WG email list. As initiation of GDPR enforcement is now less than one month away time is of the essence in transmitting
this information.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you and best regards,<o:p></o:p></p>
<p class="MsoNormal">Philip & Kathy<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Philip S. Corwin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Policy Counsel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">VeriSign, Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:"Arial","sans-serif"">12061 Bluemont Way<br>
Reston, VA 20190<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">703-948-4648/Direct<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">571-342-7489/Cell<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-family:"Arial","sans-serif"">"Luck is the residue of design" -- Branch Rickey<o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><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"><b>From:</b> Corwin, Philip <br>
<b>Sent:</b> Friday, April 06, 2018 11:03 AM<br>
<b>To:</b> 'john.mcelwaine@nelsonmullins.com' <john.mcelwaine@nelsonmullins.com>; 'gnso-rpm-wg@icann.org' <gnso-rpm-wg@icann.org><br>
<b>Subject:</b> Response from the Co-Chairs RE: Proposal to Shift URS review to Phase II<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear John:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for your submission regarding a variety of proposed changes to this Working Group’s Charter. Our understanding from discussions with staff is that, while there is no set requirement for the level of support within a WG required
to request that GNSO Council consider a Charter revision, such revisions are relatively rare and have in the past been supported by a substantial majority of WG members in the absence of significant opposition prior to transmission to Council for its consideration.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We therefore strongly encourage all WG members to carefully review your proposal and, regardless of whether one supports or opposes it, to provide some feedback to the full WG email list so that we can begin to gauge overall support. Such
email discussion can be preliminary to a full WG oral discussion on a call sometime in late April or early May, if there are indications of substantial support within the WG and a desire to engage in further discussion. The full WG will resume its regular
Wednesday calls by mid-April (we anticipate April 18), after the URS Documents, Practitioners and Providers sub-teams have completed their current work.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We also note that your proposal raises multiple issues, including:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:1.0in;text-indent:-.25in;line-height:105%;mso-list:l4 level1 lfo1">
<![if !supportLists]><span style="font-size:10.0pt;line-height:105%;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Amendment of the WG Charter to move the URS review and recommendations to Phase II<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:1.0in;text-indent:-.25in;line-height:105%;mso-list:l4 level1 lfo1">
<![if !supportLists]><span style="font-size:10.0pt;line-height:105%;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Amendment of the WG Charter to define issues that must, may, and may not be addressed<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:1.0in;text-indent:-.25in;line-height:105%;mso-list:l4 level1 lfo1">
<![if !supportLists]><span style="font-size:10.0pt;line-height:105%;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Adjustment of the WG Charter to provide additional guidance on the scope of URS and UDRP Review<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:1.0in;text-indent:-.25in;line-height:105%;mso-list:l4 level1 lfo1">
<![if !supportLists]><span style="font-size:10.0pt;line-height:105%;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Adjustment of the WG leadership structure for Phase II<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:1.0in;text-indent:-.25in;line-height:105%;mso-list:l4 level1 lfo1">
<![if !supportLists]><span style="font-size:10.0pt;line-height:105%;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Potential pause in the start of Phase II keyed to GDPR impact understanding<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These are all major issues and we encourage WG members to comment on all of them.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, regardless of whether there is substantial support within the WG for any of the elements of your proposal, we agree that the impending enforcement of GDPR raises substantial WHOIS data access issues for trademark owners and for
URS and UDRP dispute resolution providers. The issues for trademark owners are currently being discussed within the full ICANN community regarding interim and final compliance models, the latter involving accreditation and tiered data access.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In regard to the ability of URS and UDRP providers to continue to have access to the data elements necessary to fulfill their dispute resolution provider (DRP) roles, it is our intent to prepare a draft letter to ICANN’s CEO noting that
such continued access for DRPs is essential to maintaining these non-judicial alternatives for addressing trademark infringement in the DNS, and requesting that ICANN raise this important matter in its continuing discussions with EU Data Protection Authorities.
We will work with staff to prepare this draft letter and then share it with WG members for review and comment, after which we will coordinate with Council Leadership and the WG Liaison regarding transmission of a final text to ICANN management.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, <o:p></o:p></p>
<p class="MsoNormal">Philip & Kathy<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:105%"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Philip S. Corwin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Policy Counsel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">VeriSign, Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:"Arial","sans-serif"">12061 Bluemont Way<br>
Reston, VA 20190<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">703-948-4648/Direct<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">571-342-7489/Cell<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-family:"Arial","sans-serif"">"Luck is the residue of design" -- Branch Rickey<o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><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"><b>From:</b> gnso-rpm-wg [<a href="mailto:gnso-rpm-wg-bounces@icann.org">mailto:gnso-rpm-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>John McElwaine<br>
<b>Sent:</b> Thursday, April 05, 2018 9:55 PM<br>
<b>To:</b> gnso-rpm-wg <<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] [gnso-rpm-wg] Proposal to Shift URS review to Phase II<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear RPM Working Group:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In our meeting in San Juan, Puerto Rico, I raised the issue of moving the work set forth in this Working Group’s charter relating to the URS to Phase II. The Chairs asked that I put something in writing detailing the specific recommendation
and reasoning, which I present below and have also attached hereto in a Word document for your review and consideration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kind regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Proposal to Shift URS from Phase I to Phase II:<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l5 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>On 15 December 2011, the GNSO Council requested that eighteen (18) months after the launch of the New gTLD Program ICANN staff prepare and publish an Issue Report on the state of all rights protection mechanisms implemented for both
existing and new gTLDs, including but not limited to the UDRP and URS. The Council subsequently agreed to extend the timeline for a report by a further six (6) months.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p> </o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l7 level1 lfo3">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>On 9 October 2015, a Preliminary Issues Report was published discussing the scope of this potential PDP and outlining three possible options for moving forward. The third option ultimately was elected at that time:<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:.5in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
The “third option would be to conduct a policy review of all the RPMs in two phases, with the initial phase being a review only of the RPMs developed for the New gTLD Program. . . . The second, subsequent phase of work would be a review of the UDRP, based on
the concerns specific to its scope that were raised in the 2011 GNSO Issue Report and any additional relevant topics derived from the first phase of work concerning the RPMs developed for the New gTLD Program.” <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:.5in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<o:p> </o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l11 level1 lfo4">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>On 15 March 2016, the two phase approach was approved in the Charter for the Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group (“RPM Working Group”). Phase One was to focus on a review of all the RPMs
that were developed for the New gTLD Program, and Phase Two will focus on a review of the UDRP.<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l9 level1 lfo5">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The Objective & Goals in the PDP’s Charter were to examine (i) the RPMs effectiveness, (ii) whether the RPMs collectively fulfil their purposes, and (iii) whether additional policy specific recommendations are needed, including to clarify
and unify the policy goals. RPM Working Group Charter, at p. 3. The Objectives & Goals in the PDP’s Charter were broadly defined: <o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:.5in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
“In addition to an assessment of the effectiveness of each RPM, the PDP Working Group is expected to consider, at the appropriate stage of its work, the overarching issue as to whether or not all the RPMs collectively fulfill the purposes for which they were
created, or whether additional policy recommendations are needed, including to clarify and unify the policy goals. If such additional policy recommendations are needed, the Working Group is expected to develop recommendations to address the specific issues
identified. The Working Group is also directed to bear in mind that a fundamental underlying intention of conducting a review of all RPMs in all gTLDs is to create a framework for consistent and uniform reviews of these mechanisms in the future.”<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l3 level1 lfo6">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>However, the RPM Working Group Charter also contains a lengthy attachment entitled “LIST OF POTENTIAL ISSUES FOR CONSIDERATION IN THIS PDP” This “list was derived from various community suggestions in different forums, they are not listed
in any particular order of importance nor has staff attempted to analyze the merits, relevance or significance of each issue”. This list contains topics that are out of scope when compared with the Objectives and Goals, including:<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l10 level2 lfo7">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Are generic dictionary words being adequately protected so that they are available for all to use as allowed under their national laws and international treaties? E.g. sun, window<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l10 level2 lfo7">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Should monetary damages be awarded? <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l10 level2 lfo7">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Are last names and geographic places adequately protected so that they are available for all to use as allowed under their national laws, e.g, Smith, McDonald, Capitol Hill Cafe, Old Town Deli?<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l10 level2 lfo7">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Should injunctive relief be available?<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l10 level2 lfo7">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Now that Reverse Domain Name Hijacking is a regular finding of UDRP panels, indicating that domain name registrants are being abused by complaints brought against them in the UDRP process, what penalties and sanctions should be imposed
on Complainants found to be reverse domain name hijackers? How can those penalties and sanctions be aligned so as to be fair, as compared to the loss of a domain name taken from a registrant found to be a “cybersquatter”?<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l12 level1 lfo8">
<![if !supportLists]><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Issues from this list and other new out of scope issues, complaints and modifications are causing the work of the RPM Working Group to slow and are polarizing the members; thus, harming the ability to achieve consensus in the Working
Group. As recommend by the PDP breakout group and discussed by the Community in attendance at the Sunday gNSO Working Session in San Juan, it would be particularly useful if working group charters would:<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l6 level2 lfo9">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Define clearly what success for the proposed working group ”should look like”. (K. Kleiman reporting on breakout session, Transcript ICANN61 San Juan GNSO Working Session Part 2 Sunday, 11 March 2018 at 10:30 AS (“Transcript”) at p.
5).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l6 level2 lfo9">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Define topics or issues that must be addressed, may be addressed and may not be addressed. (Transcript at p. 4).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l6 level2 lfo9">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Have “more defined issues, [be] more bounded, more limited.” (Transcript at p. 5).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l6 level2 lfo9">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Have a narrower scope and be broken up into separate projects. (Transcript at p. 5).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l6 level2 lfo9">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Having a charter drafting team that “that are experts, and that might mean a legal expert, but we should also have people that have experience, practical experience.” (S. DelBianco reporting on breakout session, Transcript at p. 5).<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo10">
<![if !supportLists]><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The Trademark Clearinghouse, Sunrise and Trademark Claims Notices are RPMs relating to the registration process of domain names in the new gTLDs. The URS is more akin to the UDRP, and like the UDRP is a mandatory dispute resolution
proceeding to recover a domain name that has been clearly registered in bad faith. Since the URS is intended to be complementary of the UDRP and will have similar issues it would be more efficient to address these RPMs in a more cohesive manner.<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l2 level1 lfo11">
<![if !supportLists]><span style="mso-list:Ignore">8.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>With respect to the URS and UDRP, The European Parliament, the Council of the European Union, and the European Commission have enacted a new data privacy regulation in 2016 entitled the General Data Protection Regulation (GDPR) that
will likely adversely impact the ability of the URS and UDRP to function as these policies are currently implemented. The new regulation is scheduled to take effect on May 25, 2018. Among other ways, GDRP may adversely impact the URS and the UDRP by:
<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level2 lfo12">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Procedure for UDRP/URS: <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo12">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Possibility that Providers cannot serve the UDRP/URS Complaint if an email address cannot be obtained.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo12">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Possibility that the Language of the URS proceeding cannot be determined.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level2 lfo12">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Procedure for URS: <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo13">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Possibility that the URS provider cannot translate the notice of URS complaint into the predominant language used in the Registrant’s country or territory.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo13">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Possibility that URS complainants cannot know the language of a possible response.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo13">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Possibility that URS complainants do not know whether the URS complaint was translated into the correct language(s) and that proceedings were administered correctly.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level2 lfo13">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>UDRP Element 2 / URS: <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo14">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot argue that the registrant is not commonly known by the Domain Name at issue.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo14">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if the registrant has been authorized by the Trademark holder.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo14">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if the registrant is an authorized reseller of the Trademark holder’s product.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo14">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine on what date the domain name was “registered” by the current domain name holder if it was transferred to this current domain name holder. (requires being able to see the WhoIs history). This could prevent baseless
claims from being filed.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level2 lfo14">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>UDRP Element 3: <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo15">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if registrant has engaged in a pattern of bad faith registrations. Rule 4(b)(ii).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo15">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if registrant has been found to engage other unlawful actions, such as malware, phishing or scams.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo15">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if the registrant is in a particular geographic region to be better assess the possibility of legitimate co-existence (thus possibly even foregoing the filing of a case, and response, in the first place).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l1 level3 lfo15">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Cannot determine if the registrant is technically a “competitor” that has registered the Domain Name for the purpose of disrupting the business of the Complainant. Rule 4(b)(iii).<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l8 level1 lfo16">
<![if !supportLists]><span style="mso-list:Ignore">9.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Due to GDPR compliance issues, ICANN org is considering substantial changes to WhoIs, and has published an Interim Model for GDPR Compliance, e.g. "The CookBook" which proposes to significantly limit the public display of WhoIs data
after May 25, 2018." see: <a href="https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf">
https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf</a>. Aggressive current timelines for tiered access to WhoIs data that might provide some fix for the above issues is December 2018. There is no question that GDPR will
require policy consideration relating to the URS and UDRP that cannot be predicted and analyzed at this time.
<o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt">Recommendation: <o:p></o:p></p>
<p class="null" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt;text-indent:-.25in">
1.<span style="font-size:7.0pt"> </span>The RPM Working Group finishes its already well-advanced work and issues an Initial Report on the PDDRP, Trademark Clearinghouse, Sunrise, and Trademark Claims Notices for public comment.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt;text-indent:-.25in">
2.<span style="font-size:7.0pt"> </span>After comments have been analyzed for those elements, that the RPM Working Group finishes its work and issues its Final Report on the PDDRP, Trademark Clearinghouse, Sunrise, and Trademark Claims Notices.<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt;text-indent:-.25in">
3.<span style="font-size:7.0pt"> </span>The RPM Working Group issues a request through its Appointed Working Group Liaison to the GNSO Council to amend the RPM Working Group Charter as follows:<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt;text-indent:-.25in">
1.<span style="font-size:7.0pt"> </span>shift the work related to the URS to Phase II and, if necessary, pause starting Phase II until after the permanent impacts of GDPR on the URS and UDRP are known;<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt;text-indent:-.25in">
2.<span style="font-size:7.0pt"> </span>provide clear guidance to the WG on the issues that (i) must be addressed, (ii) may be addressed, and (iii) may not be addressed;<o:p></o:p></p>
<p class="null" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt;text-indent:-.25in">
3.<span style="font-size:7.0pt"> </span>provide clear guidance on the scope of the review of the URS and UDRP.<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Although a separate issue from this proposal, it is also recommended that Phase II Working Group has one chairperson with appropriate neutrality and experience in PDP
consensus building and parliamentary procedures. Assistance to the chair can be provided by utilizing vice-chairs and well-structured sub-teams.
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="370" style="width:277.5pt">
<tbody>
<tr>
<td width="100%" colspan="2" style="width:100.0%;padding:0in 0in 14.25pt 0in">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt;border:solid windowtext 1.0pt;padding:0in"><img border="0" width="261" height="30" id="_x0000_i1025" src="cid:image001.jpg@01D3DE37.E94C0FC0" alt="Image removed by sender. http://www.nelsonmullins.com/img/ecard-logo.png"></span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"><o:p></o:p></span></b></p>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <o:p></o:p></span></b></p>
</td>
<td width="365" style="width:273.75pt;padding:0in 0in 0in 0in">
<div style="border:none;border-top:solid #D1D2D4 1.5pt;padding:12.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:3.0pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">JOHN C. MCELWAINE </span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#659BC5;letter-spacing:.75pt">PARTNER</span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">
<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal" style="margin-bottom:6.75pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"><a href="mailto:john.mcelwaine@nelsonmullins.com"><span style="font-size:7.0pt;color:#676D72;text-decoration:none">john.mcelwaine@nelsonmullins.com</span></a>
<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">LIBERTY CENTER | SUITE 600
<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">151 MEETING STREET | CHARLESTON, SC 29401<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:5.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">T</span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <span style="text-transform:uppercase">843.534.4302</span>
</span></b><b><span style="font-size:5.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">F</span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <span style="text-transform:uppercase">843.722.8700</span>
<o:p></o:p></span></b></p>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <o:p></o:p></span></b></p>
</td>
<td width="365" style="width:273.75pt;padding:9.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">101 CONSTITUTION AVENUE, NW | SUITE 900<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">WASHINGTON, D.C., 20001<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:4.5pt"><b><span style="font-size:5.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">T</span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <span style="text-transform:uppercase">202.689.2939</span>
</span></b><b><span style="font-size:5.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt">F</span></b><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <span style="text-transform:uppercase">202.689.2862</span>
<o:p></o:p></span></b></p>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"> <o:p></o:p></span></b></p>
</td>
<td width="365" style="width:273.75pt;padding:0in 0in 0in 0in">
<div style="border:none;border-bottom:solid #D1D2D4 1.5pt;padding:0in 0in 16.0pt 0in">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676D72;letter-spacing:.75pt"><a href="http://www.nelsonmullins.com"><span style="color:#676D72;text-decoration:none">NELSONMULLINS.COM</span></a> <a href="http://www.nelsonmullins.com/people/john-mcelwaine/vcard"><span style="color:#659BC5;text-decoration:none">VCARD</span></a> <a href="http://www.nelsonmullins.com/people/john-mcelwaine"><span style="color:#355989;text-decoration:none">VIEW
BIO</span></a> <o:p></o:p></span></b></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Confidentiality Notice<o:p></o:p></p>
<p>This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.<o:p></o:p></p>
<p>If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply
to this e-mail and delete all copies of this message.<o:p></o:p></p>
</div>
<p> </p>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New Roman"">World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected
information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.
<o:p></o:p></span></p>
</div>
</body>
</html>