<div dir="ltr"><div class="gmail_extra">hi,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks Kathy for the suggestions!</div><div class="gmail_extra">councilors have until 2000 UTC this Friday 24 FEB to suggest comments or edits. so can we review the suggestions and we can submit them to the council list as input from NCSG. please if you have any other comments or suggestion, please suggest some wording for the document.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik<br>
<br><div class="gmail_quote">2017-02-22 22:40 GMT+09:00 Kathy Kleiman <span dir="ltr"><<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Tx you, Stephanie for cc'ing me. I don't think this scope goes
far enough -- and I don't see any questions asking about the
protections for Registrants. We worked very hard in Whois Review
Team One to ensure that the inquiry was balanced and that everyone
knew that Whois investigations, disclosures and compilations could
hurt those Noncommercial Registrants and others who use the DNS
for free speech, free expression, fair use and fair dealing and
other forms of treasured communication -- including speech
critical to governments, corporations, even ICANN!</p>
<p>Accordingly, I look at the list below and wonder (<font color="#ff0000">in red</font>) about whether it can be expanded
to at least be balanced and not completely one-sided in its review
(e.g., how much can we give those who complain (IP and LE)? <b><i>Q</i></b><b><i>uick
note that I have no idea how to take these suggestions to
those who can process them -- do you? Can you?</i></b></p>
<p>Best, Kathy<br>
</p>
<p>
</p>
<p>
</p><ul>
<ul>
<li>
<p style="margin-bottom:0in">Whether RDS efforts meet the
“legitimate needs of law enforcement, promoting consumer
trust and safeguarding registrant data.” </p>
</li>
<li><font color="#ff0000">Whether RDS effort protect the legitimate
rights of registrants - individuals, noncommercial
organizations, small businesses and others, in their right
to communicate political, personal, research, hobby and
educational ideas with the privacy granted under national
laws and consistent with the best free expression traditions
of the world. <br>
</font></li>
<li>
<p style="margin-bottom:0in">How RDS current & future
recommendations might be improved and better coordinated<font color="#ff0000"> for the benefit of all stakeholders. <br>
</font></p>
</li>
<li>
<p style="margin-bottom:0in">Privacy and Proxy Services
Accreditation Issues and Implementation </p>
</li>
<ul>
<li><font color="#ff0000">How was the balance achieved in
this long and painstaking Working Group? (with over
10,000 comments)<br>
</font></li>
<li><font color="#ff0000">Has implementation under the
direction of ICANN Staff and a much smaller team of
volunteers fulfilled (or not) the goals of the PPSAI
Working Group<br>
</font></li>
</ul>
<li>
<p style="margin-bottom:0in">Compliance enforcement
actions, structure, and processes</p>
</li>
<ul>
<li><font color="#ff0000">Where are the Due Process
Protections for registrants?</font></li>
<li><font color="#ff0000">Where is ICANN Compliance in
ensuring that registrants know when their domain names
are being investigated (e.g., ensuring that registrars
contact registrants re: investigation in a timely manner
and with information about how to respond, and if not
ICANN handles this function)?</font></li>
<li><font color="#ff0000">How does ICANN Compliance evaluate
complaints for harassment and "bullshit factor" --
someone reporting something in the Whois record that
does not impact the reliability of the data or the
reachability of the registrant (e.g., a student not
having a cell phone due to financial constraints, but
otherwise COMPLETELY reachable by email, regular mail,
etc.)?</font></li>
<li><font color="#ff0000">How can a registrant appeal a
takedown of his/her/its domain name by ICANN Compliance
-- and even investigate the details (registrants are
going in circles trying to understand how their domain
names disappeared).</font></li>
<li><font color="#ff0000">What steps can Compliance take to
throw out abuse by those filing complaints? How can
Compliance let the community know these anti-abuse steps
are being taken? <br>
</font></li>
</ul>
<li>
<p style="margin-bottom:0in">Availability of transparent
enforcement of contractual obligations data </p>
</li>
<li>
<p style="margin-bottom:0in">The value and timing of RDAP
as a replacement protocol </p>
</li>
<li>
<p style="margin-bottom:0in">The effectiveness of any other
steps ICANN Org has taken to implement WHOIS
Recommendations </p>
</li>
<li><font color="#ff0000">How have changes in law, high level
court decision, adoption of data protection laws
worldwide, etc, changed the legal framework of Whois and RDS
data since the original Whois Review Team Report and how
does this impact ICANN's work going forward.</font></li>
<li><font color="#ff0000"><br>
</font></li>
</ul>
</ul>
<p></p><div><div class="gmail-h5">
<div class="gmail-m_4458283681327192644moz-cite-prefix">On 2/20/2017 6:15 PM, Stephanie Perrin
wrote:<br>
</div>
<blockquote type="cite">
<p><font size="+1"><font face="Lucida Grande">Please note this is
our last kick at this can. I really don't have much
guidance; I don't quite understand exactly what we are going
to study.....but I like the idea of 6 months. Copying Kathy
who co-chaired the last one, she is most likely to be able
to figure out if this will work....<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<div class="gmail-m_4458283681327192644moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="gmail-m_4458283681327192644moz-email-headers-table" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Subject:
</th>
<td>[council] RDS Scope Guidance</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Date:
</th>
<td>Mon, 20 Feb 2017 19:31:56 +0000</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">From:
</th>
<td>James M. Bladel <a class="gmail-m_4458283681327192644moz-txt-link-rfc2396E" href="mailto:jbladel@godaddy.com"><jbladel@godaddy.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">To: </th>
<td>GNSO Council List <a class="gmail-m_4458283681327192644moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div class="gmail-m_4458283681327192644WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Councilors
–<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Attached,
please find a draft RDS Scope Guidance document, which
consolidates the feedback received from all SOs and ACs on
guidance/recommendations to limit the scope of the
upcoming RDS (WHOIS) review. Time is tight, so if you
have any comments or edits, please respond by <b>2000 UTC
this Friday 24 FEB.</b><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Once
completed, the RDS Scope Guidance document will be
distributed to RDS Review Team applicants, to confirm that
they are still interested in serving on this review team.
There is also a proposal to extend the call for
applications until 7 MAR.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Thank you,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">J.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
</div>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
<br></blockquote></div><br></div></div>