<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Paul,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I'm not sure why you say this is precise. Is there one criterion in particular that caused you to say that?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 6, 2018 at 9:24 AM, Paul Tattersfield <span dir="ltr"><<a href="mailto:gpmgroup@gmail.com" target="_blank">gpmgroup@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="m_-5218840697328733498gmail-im"><span class=""><span class="m_-5218840697328733498gmail-im"><div><i>it is also recommended that Phase II Working Group has one chairperson with
appropriate neutrality and experience in PDP consensus building and
parliamentary procedures<br><br></i></div></span></span>That is quite a precise skill set, did you have someone in mind?<i><br></i><div class="m_-5218840697328733498gmail-yj6qo m_-5218840697328733498gmail-ajU"><div class="m_-5218840697328733498gmail-ajR" id="m_-5218840697328733498gmail-:sy"><img src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif" class="m_-5218840697328733498gmail-ajT"></div></div></span><i><br></i></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Apr 6, 2018 at 2:54 AM, John McElwaine <span dir="ltr"><<a href="mailto:john.mcelwaine@nelsonmullins.com" target="_blank">john.mcelwaine@nelsonmullins.<wbr>com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="m_-5218840697328733498m_-834285580043357222WordSection1">
<p class="MsoNormal">Dear RPM Working Group:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Kind regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">John<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></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:<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"><u></u> <u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="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.” <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:.5in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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: <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="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.”<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>5.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Should monetary damages be awarded? <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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?<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Should injunctive relief be available?<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>5.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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”?<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <wbr> <wbr> <wbr> <wbr> <wbr> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>6.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Define topics or issues that must be addressed, may be addressed and may not be addressed. (Transcript at p. 4).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Have “more defined issues, [be] more bounded, more limited.” (Transcript at p. 5).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Have a narrower scope and be broken up into separate projects. (Transcript at p. 5).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>5.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>7.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>8.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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:
<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Procedure for UDRP/URS:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Possibility that Providers cannot serve the UDRP/URS Complaint if an email address cannot be obtained.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Possibility that the Language of the URS proceeding cannot be determined.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Procedure for URS:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Possibility that the URS provider cannot translate the notice of URS complaint into the predominant language used in the Registrant’s country or territory.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Possibility that URS complainants cannot know the language of a possible response.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Possibility that URS complainants do not know whether the URS complaint was translated into the correct language(s) and that proceedings were administered correctly.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>UDRP Element 2 / URS:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Cannot argue that the registrant is not commonly known by the Domain Name at issue.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Cannot determine if the registrant has been authorized by the Trademark holder.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Cannot determine if the registrant is an authorized reseller of the Trademark holder’s product.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>UDRP Element 3:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Cannot determine if registrant has engaged in a pattern of bad faith registrations. Rule 4(b)(ii).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Cannot determine if registrant has been found to engage other unlawful actions, such as malware, phishing or scams.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><span>4.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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).<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><span>9.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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" target="_blank">
https://www.icann.org/en/syste<wbr>m/files/files/gdpr-compliance-<wbr>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.
<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt">Recommendation: <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin:0in;margin-bottom:.0001pt"> <u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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.<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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:<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>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;<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>provide clear guidance to the WG on the issues that (i) must be addressed, (ii) may be addressed, and (iii) may not be addressed;<u></u><u></u></p>
<p class="m_-5218840697328733498m_-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
<u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>provide clear guidance on the scope of the review of the URS and UDRP.<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><u></u> <u></u></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.
<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<table class="m_-5218840697328733498m_-834285580043357222MsoNormalTable" style="width:277.5pt" border="0" cellpadding="0" cellspacing="0" width="0">
<tbody>
<tr>
<td colspan="2" style="width:100.0%;padding:0in 0in 14.25pt 0in" width="100%">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"><img id="m_-5218840697328733498m_-834285580043357222_x0000_i1025" src="http://www.nelsonmullins.com/img/ecard-logo.png" alt="http://www.nelsonmullins.com/img/ecard-logo.png" border="0" height="30" width="261"></span></b><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"><u></u><u></u></span></b></p>
</td>
</tr>
<tr>
<td style="width:3.75pt;padding:0in 0in 0in 0in" width="5">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"> <u></u><u></u></span></b></p>
</td>
<td style="width:273.75pt;padding:0in 0in 0in 0in" width="365">
<div style="border:none;border-top:solid #d1d2d4 1.5pt;padding:12.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:3.0pt;border:none;padding:0in"><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">
<u></u><u></u></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" target="_blank"><span style="font-size:7.0pt;color:#676d72;text-decoration:none">john.mcelwaine@nelsonmullins.c<wbr>om</span></a>
<u></u><u></u></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
<u></u><u></u></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<u></u><u></u></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>
<u></u><u></u></span></b></p>
</td>
</tr>
<tr>
<td style="width:3.75pt;padding:0in 0in 0in 0in" width="5">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"> <u></u><u></u></span></b></p>
</td>
<td style="width:273.75pt;padding:9.0pt 0in 0in 0in" width="365">
<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<u></u><u></u></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<u></u><u></u></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>
<u></u><u></u></span></b></p>
</td>
</tr>
<tr>
<td style="width:3.75pt;padding:0in 0in 0in 0in" width="5">
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"> <u></u><u></u></span></b></p>
</td>
<td style="width:273.75pt;padding:0in 0in 0in 0in" width="365">
<div style="border:none;border-bottom:solid #d1d2d4 1.5pt;padding:0in 0in 16.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#676d72;letter-spacing:.75pt"><a href="http://www.nelsonmullins.com" target="_blank"><span style="color:#676d72;text-decoration:none">NELSONMULLINS.COM</span></a> <a href="http://www.nelsonmullins.com/people/john-mcelwaine/vcard" target="_blank"><span style="color:#659bc5;text-decoration:none">VCARD</span></a> <a href="http://www.nelsonmullins.com/people/john-mcelwaine" target="_blank"><span style="color:#355989;text-decoration:none">VI<wbr>EW
BIO</span></a> <u></u><u></u></span></b></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p>Confidentiality Notice</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.</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.</p>
</div>
<br></div></div><span class="">______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rpm-wg</a><br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</a><br></blockquote></div><br></div>