<div dir="ltr">One way in which the URS burden of proof differs substantially from UDRP is that the URS requires that "For a URS matter to conclude in favor of the Complainant, the Examiner shall render a Determination that there is<u> no genuine issue of material fact</u>." (URS Procedure 8.3). This is the same burden as the URS summary judgment.<div><br><div>It bears noting that I haven't seen this language mentioned by any URS arbitrator in any cases which I've reviewed. </div></div><div><br></div><div>Jonathan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 16, 2018 at 7:49 AM, BECKHAM, Brian <span dir="ltr"><<a href="mailto:brian.beckham@wipo.int" target="_blank">brian.beckham@wipo.int</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="m_8798512842824124372WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Hi Jon,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Could you explain/unpack that a little bit.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Some folks might see “standard of review” and “burden of proof” as somewhat synonymous, in which case as you rightly point out the URS applies a “clear and convincing” standard
but the UDRP applies a “balance of probabilities” (sometimes called “on balance”) standard.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Or are you referring to the standard of review for appeals cases?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Sorry for a perhaps basic question, and thanks!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Brian
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></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:<a href="mailto:gnso-rpm-wg-bounces@icann.org" target="_blank">gnso-rpm-wg-bounces@<wbr>icann.org</a>]
<b>On Behalf Of </b>Jon Nevett<br>
<b>Sent:</b> Friday, April 13, 2018 8:43 PM<br>
<b>To:</b> Nahitchevansky, Georges<br>
<b>Cc:</b> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [gnso-rpm-wg] Proposal to Shift URS review to Phase II<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">One alternative is to split the URS review into two parts. <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As most know, the standard of review of a URS claim is exactly the same as a UDRP claim. The burden of proof, however, is higher, as URS was supposed to be for "slam dunk" cases -- hence the the clear and convincing burden. We could wait
on reviewing the URS standard of review and everything that goes with that, as that work will mirror the work that will need to be completed during the UDRP review. We could continue to review the facets of the URS that differ from the UDRP now and push the
rest to later. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Just an idea for a middle ground if folks want one. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div><div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Jon<u></u><u></u></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div class="h5">
<div>
<p class="MsoNormal">On Apr 13, 2018, at 2:25 PM, Nahitchevansky, Georges <<a href="mailto:ghn@kilpatricktownsend.com" target="_blank">ghn@kilpatricktownsend.com</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div><div><div><div class="h5">
<div>
<p class="MsoNormal"><a name="m_8798512842824124372__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">+1 on moving the URS to phase 2. Georges N</span></a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span class="m_8798512842824124372apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></span><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"><span style="color:purple">mailto:gnso-rpm-wg-bounces@<wbr>icann.org</span></a>]<span class="m_8798512842824124372apple-converted-space"> </span><b>On Behalf Of<span class="m_8798512842824124372apple-converted-space"> </span></b>Kurt Pritz<br>
<b>Sent:</b><span class="m_8798512842824124372apple-converted-space"> </span>Friday, April 13, 2018 2:06 PM<br>
<b>To:</b><span class="m_8798512842824124372apple-converted-space"> </span><a href="mailto:gnso-rpm-wg@icann.org" target="_blank"><span style="color:purple">gnso-rpm-wg@icann.org</span></a><br>
<b>Subject:</b><span class="m_8798512842824124372apple-converted-space"> </span>Re: [gnso-rpm-wg] Proposal to Shift URS review to Phase II</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Hi John (and everyone):<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Thank you to John for taking the time to put together this cogent document. <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">I support moving the URS discussion to phase II for the reasons John cited and others.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">As John, and others (in an earlier email string) have pointed out, the results of GDRP could affect the URS discussion. The next round of new gTLDs should not be held hostage to that. <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">For me, I see no reason why the URS discussion was ever on the critical path to the next round of new gTLDs. <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">The findings of this working group will not affect the analysis of a potential gTLD applicant regarding whether to apply or setting up operations. Nor will it affect the evaluation of applications. If registries receive a URS decision,
they will implement it. They have no role in setting the criteria or requirements for URS decision making. Therefore, there is no reason to put this discussion on the critical path to the next round.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">John’s paper alludes to this when he says that URS is a lot more like UDRP (which is in Phase II) than TMCH & Claims (which is in Phase I). <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">While this phase I / phase II timing decision might not have seemed to be a critical decision at the outset, GDRP developments and the length of time taken so far has made it a critical decision.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">I find George’s reasoning unpersuasive. He cites section 5 of John’s paper, which is essentially background information — dicta with regard to he matter at hand. All of the questions in section 5 can be taken up by this working group regardless
of the timing and none of the questions need be on the critical path to the next round for the reason stated above (i.e., the new gTLD applicant or operator is not affected by the outcome of these discussion topics).<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Similarly, I don’t think George’s discussion regarding fpast meeting frequency is relevant to whether to move the URS to phase II. <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">I find the discussion of the chairmanship irrelevant to the discussion also. <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Thanks again to John for doing this work, I support his conclusion that the URS discussion should be moved to phase II.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Kurt<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div></div><div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div class="h5">
<div>
<div>
<p class="MsoNormal">On Apr 13, 2018, at 9:12 AM, Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank"><span style="color:purple">gpmgroup@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div></div><div><div><div class="h5">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Greg,<br>
<br>
It’s always important to try and be precise in what you say. I think it would have been helpful for John to clarify his proposal as he has not done so, on a more general level:<span class="m_8798512842824124372apple-converted-space"> </span><br>
<br>
Clearly the 3 qualities John identified are important basic competencies.<span class="m_8798512842824124372apple-converted-space"> </span><br>
<br>
I agree one of the highest compliments one can give a WG chair is that you had no sense of where they stood on any of the issues the group handled. The question is how can this be achieved more often than not and will the 3 qualities John identified be sufficient?<br>
<br>
I would suggest character traits high in openness and agreeableness are probably as important if not more important. If these could be combined with humility, a moral compass and intellect this may help avoid working group member fatigue and in the worst case
all the time consuming curative work necessary to address a situation where someone has fallen below the required standards.<br>
<br>
Kind regards,<br>
<br>
<br>
Paul.<u></u><u></u></p>
</div>
</div></div><div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div><div><div class="h5">
<div>
<p class="MsoNormal">On Mon, Apr 9, 2018 at 4:02 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="color:purple">gregshatanipc@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div><div><div class="h5">
<div>
<div>
<p class="MsoNormal">Paul,<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Perhaps John can clarify what he meant by these criteria. I think they make perfect sense and seem like common sense. As I read them, they are fairly common criteria for good ICANN GNSO Working Group chairs and nothing surprising. By
your reaction, I suspect you are reading them differently, especially since you think that these create a heightened potential to shape process in an unwelcome way (I say “heightened” only because any chair has some potential to process in a way that is unwelcome
to some). That may be the source of our different views on these criteria.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Appropriate neutrality = Someone who is able to act neutral as expected of Working Group chairs, as if they had no interest in any particular outcome. Not someone who is in fact neutral (i.e., not a stakeholder at all, or a stakeholder
in a community that truly has no preference as to outcome); this latter type would be relatively rare. I think one of the highest compliments one can give a WG chair is that you had no sense of where they stood on any of the issues the group handled.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Experience in PDP consensus-building = Ideally, a former chair, vice-chair, subgroup chair, rapporteur or other leader/facilitator in a GNSO PDP WG, who has already had the experience of trying to aid the WG (or subgroup) to come to consensus.
Less ideally, an experienced GNSO WG PDP participant, who has been through some number of consensus building processes and is ready to step into the chair role in that process.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Experience in parliamentary procedure = Someone with experience with and a good understanding of the rules and procedures governing the process of GNSO PDP WG meetings. Not someone who has specific experience with Robert’s Rules of Order
and its non-US equivalents, not someone who is a member of an actual Parliament, and not someone who is a “parliamentarian” (which could mean a member of parliament or someone who advises a chair on rules of procedure). This may be the one that is tripping
you up. This is probably the most susceptible to misunderstanding, since we don’t use the term “parliamentary procedure” that often in ICANN-land in any sense (and our meetings do not run by Robert’s, etc.)<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">The bigger picture I get is of a steady and experienced hand who can stay above the fray in terms of issues and positions, who can actively work with the group to identify and fashion consensus, and someone who has very good understanding
of and facility with our rules of procedure so that they can run the meetings well and make them as efficient and effective as possible, while ensuring that all positions are heard. From a procedural side, this sounds completely sensible and not that uncommon
in ICANN-land.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Thoughts?<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888"> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888">Greg</span><u></u><u></u></p>
</div>
</div>
</div></div><div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div><div><div class="h5">
<div>
<div>
<p class="MsoNormal">On Mon, Apr 9, 2018 at 6:02 AM Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank"><span style="color:purple">gpmgroup@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div>
</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"><div><div class="h5">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Greg, because they are a subset of the ideal criteria necessary for optimum outcomes and as such has the potential to shape process in an unwelcome way.<br>
<br>
I am hoping John having brought forward his in depth proposal with this very significant ballon d'essai in the ultimate paragraph would expand further on his intentions or at least indicate if he had someone mind.<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Kind regards,<br>
<br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Paul.<u></u><u></u></p>
</div>
</div>
</div></div><div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div><div><div class="h5">
<div>
<p class="MsoNormal">On Fri, Apr 6, 2018 at 4:06 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="color:purple">gregshatanipc@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"><div><div class="h5">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Paul,</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span 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?</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#888888"> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#888888">Greg</span><u></u><u></u></p>
</div>
</div>
</div>
</div></div><div>
<div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div><div><div class="h5">
<div>
<p class="MsoNormal">On Fri, Apr 6, 2018 at 9:24 AM, Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank"><span style="color:purple">gpmgroup@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div><div><div class="h5">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498gmail-im">That is quite a precise skill set, did you have someone in mind?</span><u></u><u></u></p>
</div>
</div></div><div>
<div id="m_8798512842824124372m_-6284359310653908347m_-5532678702991762120m_-7151582625145430952m_-5218840697328733498gmail-:sy">
<div>
<p class="MsoNormal"><span style="border:solid windowtext 1.0pt;padding:0in"><img border="0" width="100" height="100" id="m_8798512842824124372_x0000_i1025" src="cid:~WRD000.jpg" alt="Image removed by sender."></span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div><div><div class="h5">
<div>
<div>
<div>
<p class="MsoNormal">On Fri, Apr 6, 2018 at 2:54 AM, John McElwaine <<a href="mailto:john.mcelwaine@nelsonmullins.com" target="_blank"><span style="color:purple">john.mcelwaine@nelsonmullins.<wbr>com</span></a>> wrote:<u></u><u></u></p>
</div>
</div>
</div>
</div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<div><div><div class="h5">
<div>
<p class="MsoNormal">Dear RPM Working Group:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<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>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Kind regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">John<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Proposal to Shift URS from Phase I to Phase II:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:.5in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
5.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Should monetary damages be awarded?<span class="m_8798512842824124372apple-converted-space"> </span><u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Should injunctive relief be available?<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
5.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <wbr> <wbr> <wbr> <wbr> <wbr> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
6.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Have “more defined issues, [be] more bounded, more limited.” (Transcript at p. 5).<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Have a narrower scope and be broken up into separate projects. (Transcript at p. 5).<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
5.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
7.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
8.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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:<span class="m_8798512842824124372apple-converted-space"> </span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Procedure for UDRP/URS:<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Possibility that Providers cannot serve the UDRP/URS Complaint if an email address cannot be obtained.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Possibility that the Language of the URS proceeding cannot be determined.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Procedure for URS:<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Possibility that URS complainants cannot know the language of a possible response.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>UDRP Element 2 / URS:<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Cannot argue that the registrant is not commonly known by the Domain Name at issue.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Cannot determine if the registrant has been authorized by the Trademark holder.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>Cannot determine if the registrant is an authorized reseller of the Trademark holder’s product.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>UDRP Element 3:<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
4.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
9.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>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:<span class="m_8798512842824124372apple-converted-space"> </span><a href="https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf" target="_blank"><span style="color:purple">https://www.icann.org/en/<wbr>system/files/files/gdpr-<wbr>compliance-interim-model-<wbr>08mar18-en.pdf</span></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>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Recommendation:<span class="m_8798512842824124372apple-converted-space"> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></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.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></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.<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:.75in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></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:<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
1.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></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;<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
2.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></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;<u></u><u></u></p>
<p class="m_8798512842824124372m-6284359310653908347m-5532678702991762120m-7151582625145430952m-5218840697328733498m-834285580043357222null" style="margin-right:0in;margin-bottom:0in;margin-left:1.25in;margin-bottom:.0001pt">
3.<span style="font-size:7.0pt"> <span class="m_8798512842824124372apple-converted-space"> </span></span>provide clear guidance on the scope of the review of the URS and UDRP.<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div></div><table class="m_8798512842824124372MsoNormalTable" 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">
<div>
<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="m_8798512842824124372m_-6284359310653908347m_-5532678702991762120m_-7151582625145430952m_-5218840697328733498m_-834285580043357222_x005f_x0000_i1025" src="cid:image001.jpg@01D3D589.C4A1A4C0" alt="Image removed by sender. http://www.nelsonmullins.com/img/ecard-logo.png"></span></b><u></u><u></u></p>
</div>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676d72;letter-spacing:.75pt"> </span></b><u></u><u></u></p>
</div>
</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><u></u><u></u></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.<wbr>com</span></a></span></b><u></u><u></u></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 | <a href="https://maps.google.com/?q=SUITE+600%0D%0A+%0D%0A+151+MEETING+STREET%C2%A0%7C%C2%A0CHARLESTON,%C2%A0SC%C2%A029401&entry=gmail&source=g" target="_blank"><span style="color:purple">SUITE
600<span class="m_8798512842824124372apple-converted-space"> </span></span></a></span></b><u></u><u></u></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"><a href="https://maps.google.com/?q=SUITE+600%0D%0A+%0D%0A+151+MEETING+STREET%C2%A0%7C%C2%A0CHARLESTON,%C2%A0SC%C2%A029401&entry=gmail&source=g" target="_blank"><span style="color:purple">151
MEETING STREET | CHARLESTON, SC 29401</span></a></span></b><u></u><u></u></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 class="m_8798512842824124372apple-converted-space"> </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.<wbr>8700</span> </span></b><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676d72;letter-spacing:.75pt"> </span></b><u></u><u></u></p>
</div>
</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"><a href="https://maps.google.com/?q=101+CONSTITUTION+AVENUE,+NW%C2%A0%7C%C2%A0SUITE+900+%0D%0A+WASHINGTON,+D.C.,%C2%A0%C2%A020001&entry=gmail&source=g" target="_blank"><span style="color:purple">101
CONSTITUTION AVENUE, NW | SUITE 900</span></a></span></b><u></u><u></u></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"><a href="https://maps.google.com/?q=101+CONSTITUTION+AVENUE,+NW%C2%A0%7C%C2%A0SUITE+900+%0D%0A+WASHINGTON,+D.C.,%C2%A0%C2%A020001&entry=gmail&source=g" target="_blank"><span style="color:purple">WASHINGTON,
D.C., 20001</span></a></span></b><u></u><u></u></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 class="m_8798512842824124372apple-converted-space"> </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.<wbr>2862</span> </span></b><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="5" style="width:3.75pt;padding:0in 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#676d72;letter-spacing:.75pt"> </span></b><u></u><u></u></p>
</div>
</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">
<div>
<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/" 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></span></b><u></u><u></u></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div><div><div class="h5">
<div>
<p class="MsoNormal">Confidentiality Notice<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
</div></div></div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div><div><div class="h5">
<div>
<p class="MsoNormal">______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank"><span style="color:purple">gnso-rpm-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</span></a><u></u><u></u></p>
</div>
</div></div></blockquote>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><br>
______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank"><span style="color:purple">gnso-rpm-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</span></a><u></u><u></u></p>
</div>
</div></div></blockquote>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div><div><div class="h5">
<div>
<p class="MsoNormal">______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank"><span style="color:purple">gnso-rpm-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</span></a><u></u><u></u></p>
</div>
</div></div></div>
</blockquote>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif""><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.<br>
<br>
</span><u></u><u></u></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif""><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.<br>
</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
</span><a href="mailto:gnso-rpm-wg@icann.org" target="_blank"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:purple">gnso-rpm-wg@icann.org</span></a><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><br>
</span><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:purple">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</span></a><u></u><u></u></p>
</div></div></div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div class="m_8798512842824124372WordSection1"><br>
<table class="m_8798512842824124372MsoTableGrid" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td valign="top"><a href="http://www.wipo.int/ip-outreach/en/ipday/index.html?utm_source=wipomail&utm_medium=signature&utm_campaign=ipday2018" target="_blank"><img width="100" height="100" id="m_8798512842824124372Picture 1" src="https://www3.wipo.int/export/sites/www3/shared/images/ipday_signature_option1.png" alt=" Colorful silhouette of a woman’s head, representing the theme of the World IP Day campaign."></a>
</td>
<td valign="top"><strong><span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#e41267">Powering change:</span><br>
<span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#e41267">Women in innovation and creativity</span><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1f3677">World Intellectual Property Day 2018</span><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#2fb7e1">April 26</span><br>
</strong><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><a href="http://www.wipo.int/ip-outreach/en/ipday/index.html?utm_source=wipomail&utm_medium=signature&utm_campaign=ipday2018" target="_blank">wipo.int/ipday</a>
<span style="color:#006fc9"> </span><span style="color:black">#worldipday</span></span>
</td>
</tr>
</tbody>
</table>
</div>
<p> </p>
<div class="m_8798512842824124372WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.
<u></u><u></u></span></p>
</div>
</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>