<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta content="text/html; charset=utf-8">
</head>
<body>
<meta content="script-src 'self'; img-src * cid: data:;">
<style id="outgoing-font-settings">
<!--
#response_container_BBPPID
{font-family:initial;
font-size:initial;
color:initial}
-->
</style>
<div id="response_container_BBPPID" dir="auto" style="outline:none">
<div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%">Surprising to me that after two plus years we are still in what appears to be the same place. If every proposal moves forward at this point, then we really have not done a very good
job as a group. All of the points in these proposals were raised in various ways over two years ago. We have had endless discussions on these items and even had subgroups look at various issues over many months and make recommendations. From what I can
tell that work was more or less ignored and swept aside and all of the stuff from two years ago is now back on the table -- including the issue as to whether the URS is fit for its purpose. Honestly, this seems like a giant waste of two years if we just rubber
stamp the same general proposals that existed for over two years. We should have just submitted all the proposals and points from two years ago for public comment and saved everyone a bunch of time over the course of two plus years (of course there are some
that might not have wanted the extra time and enjoyed dragging this out). All of this does not speak well for our working group and highlights an apparent disfunctionality in the process. I am sorry that I being harsh in this assessment, but honestly after
all this time we should be able to cull down the list of proposals to something short and manageable.</div>
<div name="BB10" id="response_div_spacer_BBPPID" dir="auto" style="width:100%"><br style="display:initial">
</div>
<div id="blackberry_signature_BBPPID" name="BB10" dir="auto">
<div id="_signaturePlaceholder_BBPPID" name="BB10" dir="auto"></div>
</div>
</div>
<div id="_original_msg_header_BBPPID" dir="auto">
<table width="100%" style="background-color:white; border-spacing:0px; display:table; outline:none">
<tbody>
<tr>
<td colspan="2" style="padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
<div style="border-right:none; border-bottom:none; border-left:none; border-top:1pt solid rgb(181,196,223); padding:3pt 0in 0in; font-family:Tahoma,"BB Alpha Sans","Slate Pro"; font-size:10pt">
<div id="from"><b>From:</b> mpsilvavalent@gmail.com</div>
<div id="sent"><b>Sent:</b> October 20, 2018 8:21 AM</div>
<div id="to"><b>To:</b> rtushnet@law.harvard.edu</div>
<div id="cc"><b>Cc:</b> gnso-rpm-wg@icann.org</div>
<div id="subject"><b>Subject:</b> Re: [GNSO-RPM-WG] URS levels of support for public comments</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
</div>
<div>
<div dir="auto">
<div>Hi all, </div>
<div dir="auto"><br>
</div>
<div dir="auto">I want to strongly support Rebecca on this, it seems the best way to solve the issue of "support" that was not clear even when we start with it. Throwing hours of debate to it wont help to reach a much more accurate set of proposals anyways.
It would almost mean going again to each proposal to check if there is "support", if we even get to agree on that. We just have to make it clear that proposala are not put out as any consensus or agreement of the group.</div>
<div dir="auto"><br>
</div>
<div dir="auto">For the record, and it is already in the meeting records, I thought and supported in the beginning that only proposals with no strong objections, or soft consensus, should move to public comment, and me and other were overun saying only "support"
was needed, so we moved on each proposal taking notes on support interventions. I agree with Rebeca that notes might not be enough to just let staff check the level of support and decide something based on that. </div>
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"> I also agree, as I stated in the call last week, that asking if the URS is fit for purpose is exactly the type of core question. We are reviewing wether thigs work or not how we planned and if we should change them. This question is absolutely
relevant to that end.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"> Best to all,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Martín Silva</div>
<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr">On Fri, Oct 19, 2018, 18:49 Tushnet, Rebecca <<a href="mailto:rtushnet@law.harvard.edu">rtushnet@law.harvard.edu</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">
<div id="m_1149365513411254074divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<p style="margin-top:0; margin-bottom:0">Following up on what I said on one of the calls, and consistent with Greg Shatan's comments (an agreement that I think should probably be noted as significant in itself), I don't think the staff categorizations have
worked. If the ultimate point is to get feedback on potential fixes that have been raised, and we don't want to spend a lot more time on this, then I would say we may need to pass on the proposals as non-consensus proposals for community feedback. As Greg
did, I supported proposals for comment that I am presently unlikely to support for adoption; based on other comments, I suspect many of us did so--which means that any staff-prepared summary of objections received is also going to be unrepresentative of the
full range of arguments against a particular proposal unless we spend a lot more time on it.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">One specific thing: t<span style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">he charter asks if the URS is fit for purpose. If you agree that the charge allows the answer "no," then one recommendation
for a fix is "make it the UDRP," if you think the game isn't worth the candle. That proposal is thus clearly within scope. </span></p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<div id="m_1149365513411254074Signature">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div><br>
</div>
Rebecca Tushnet</div>
<div style="font-family:Tahoma; font-size:13px">Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
703 593 6759 </div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
GNSO-RPM-WG mailing list<br>
<a href="mailto:GNSO-RPM-WG@icann.org" target="_blank" rel="noreferrer">GNSO-RPM-WG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></blockquote>
</div>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Black" size="1"><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>
</font><br>
<hr>
<font face="Arial" color="Black" size="1"><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>
</font>
</body>
</html>