<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>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>
</p>
<p>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>
</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 14.08.2018 um 05:46 schrieb Alan
Greenberg:<br>
</div>
<blockquote type="cite"
cite="mid:YQXPR0101MB1590CD356E3A4059F195A38E93380@YQXPR0101MB1590.CANPRD01.PROD.OUTLOOK.COM">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
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>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
RDS-WHOIS2-RT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org">RDS-WHOIS2-RT@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
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 class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">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 class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">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 class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">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 class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">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>
</body>
</html>