<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">I prefer the stronger - more direct - language.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">-Carlton</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 14, 2018 at 2:16 PM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
I beleive that the safeguarding registrant data already covers this, but
if we want something stronger, I would suggest that we:<br><br>
- Eliminate the Safeguarding requirement<br><br>
- Replace the OECD paragrapgh with a more generic requirement to review
privacy and data-transfer issues. I think the reference to the OECD
Guidelines, even with the caveate "as amended from time to
time" is appropriate in the Bylaws.<br><br>
Alan<br><br>
At 14/08/2018 07:35 AM, Volker Greimann wrote:<br><br>
<blockquote type="cite" class="m_9198056968373132258cite">After thinking a bit more on
this, I believe that we should not recommend removing this section from
the bylaws. Considering the rising importance of Privacy Protection and
Requirements on transborder flows of data, these principles should be
strengthened, not weakened in the ICANN bylaws. <br>
<br>
Consequently, the next RT will not be in the same position we are
currently in as GDPR will hopefully have been implemented by then.
<br><br>
Volker<br><br>
Am 14.08.2018 um 05:46 schrieb Alan Greenberg:<br>
<blockquote type="cite" class="m_9198056968373132258cite">Section 4.6(a)(v) of the ICANN
Bylaws specifies that each Specific Review team may recommend that may
recommend that the review in question should no longer be conducted or
should be amended.<br><br>
I determining the scope of the present RDS-WHOIS2 Review, section
4.6(e)(iii) of the Bylaws was considered:<br><br>
<dl>
<dd><i>"The review team for the Directory Service Review
("Directory Service Review Team") will consider the
Organisation for Economic Co-operation and Development ("OECD")
Guidelines on the Protection of Privacy and Transborder Flows of Personal
Data as defined by the OECD in 1980 and amended in 2013 and as may be
amended from time to time."</i>
</dd></dl>The RT decided that this section of the Bylaw mandated scope should
be omitted from the issues to be addressed, based on the complete lack of
consideration of such guidelines in the current WHOIS implementation and
the fact that at the time, an ongoing PDP was considering whether to
incorporate such guidelines on its recommendations.<br><br>
Since that decision, the discussion of RDS(WHOIS) in ICANN has evolved
and considerable focus has been targeted at the EU GDPR, its impact on
the current WHOIS, and how it will influence RDS developments.<br><br>
Given:<br><br>
- the focus on GDPR and the ongoing efforts to address this effectively
in the short to medium term;<br><br>
- the fact the OECD Guidelines have been made less relevant by the actual
regulations and laws in Europe and other jurisdictions; and<br><br>
- the more generalized requirement for the RDS Specific Review to
consider safeguards for protecting RDS data;<br><br>
the RT believes that section 4.6(e)(iii) of the ICANN Bylaws is no longer
needed.<br><br>
RECOMMENDATION:<br><br>
The ICANN Board should take action to remove ICANN Bylaws section
4.6(e)(iii).<br><br>
<br><br>
<br>
<pre>_______________________________________________
RDS-WHOIS2-RT mailing list
<a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a>
</pre></blockquote><br><br>
<pre>--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email:
<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" target="_blank">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" target="_blank">
www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a href="http://www.facebook.com/KeySystems" target="_blank">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" target="_blank">
www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese
Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns
per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact
us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email:
<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" target="_blank">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" target="_blank">
www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay
updated:
<a href="http://www.facebook.com/KeySystems" target="_blank">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" target="_blank">
www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom
it is addressed. Furthermore it is not permitted to publish any content
of this email. You must not use, disclose, copy, print or rely on this
e-mail. If an addressing or transmission error has misdirected this
e-mail, kindly notify the author by replying to this e-mail or contacting
us by telephone.
</pre><br>
_______________________________________________RDS-WHOIS2-RT mailing
list<br>
<a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a></blockquote>
</div>
_______________________________________________<br>
RDS-WHOIS2-RT mailing list<br>
<a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a><br>
</blockquote></div>