<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>How about adding: "Further procedures for resolving conflicts
with local privacy laws are included in the 2013 RAA Data
Retention specification"?<br>
</p>
<br>
<div class="moz-cite-prefix">Am 07.09.2016 um 12:52 schrieb gtheo:<br>
</div>
<blockquote cite="mid:3b5348e00a1f218a379a4340ae37c954@xs4all.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">Hello all, <br>
<br>
<em>1. Where a conflict exists between local privacy laws and
requirements included in this Policy, ICANN’s Procedure for
Handling WHOIS Conflicts with Privacy Laws is available for
Registry Operators and Registrars. </em><br>
<br>
We didn't get around this yesterday, wich is fine. Let us see if
we can have some discussion in advance about this as I am
struggling with this section for a few now. <br>
<br>
The text itself is good, as in, this is what I expected after
the discussions we had about this in the last few months. <br>
<br>
What I am not sure off is how to deal with this in the sense of
moving forward to the comment period. <br>
The procedure is not working, but is outside of this IRT to
address, yet this IRT relies on it. <br>
<br>
Are we going to put in a footnote in the report that says
something like: <br>
<em>Outside the scope of the IRT to address, but we wish the
Registrars and Registrants the best of luck!</em><br>
<br>
Thanks,<br>
Theo</div>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">Dennis Chang schreef op 2016-09-02 02:05 AM:
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">Dear Thick Whois Policy
Implementation Review Team, <br>
<br>
Attached for your review is our initial draft of the Thick
Whois<br>
Transition Policy for .COM, .NET and .JOBS. The draft Policy
includes<br>
the various elements discussed in our recent meeting on this
topic. <br>
<br>
As you review the draft, you will find bracketed text in four<br>
sections: sections 2.9, 2.10, 3.4 and 3.5. These sections are<br>
bracketed because they reference the Registry Registration
Data<br>
Directory Services Consistent Labeling and Display Policy and
the<br>
Registration Data Access Protocol gTLD Profile. As you may be
aware, a<br>
Request for Reconsideration (RfR) was submitted by the
Registries<br>
Stakeholder Group in August regarding the Registry
Registration Data<br>
Directory Services Consistent Labeling and Display Policy [<a
moz-do-not-send="true"
href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en"
target="_blank" rel="noreferrer">1</a>] that was<br>
published on 26 July 2016. The RfR objects to the inclusion of
RDAP in<br>
the Consensus Policy. While the RfR goes through its own
process, we<br>
thought it was important to continue progressing the
implementation<br>
project with the goal of opening Public Comment in September
and<br>
announcing the Transition Policy by 1 February 2017 per our
schedule.<br>
Therefore, the text is bracketed as it may need to be
revisited<br>
pending the resolution of the RfR and we wanted to directly
call the<br>
IRT’s attention to it. <br>
<br>
We will review all contents of the document at our next IRT
meeting as<br>
a team but please provide your comments in advance via email
if<br>
possible. <br>
<br>
Thank you for your support! <br>
<br>
— <br>
<br>
Kind Regards, <br>
<br>
Dennis S. Chang <br>
<br>
GDD Services & Engagement Program Director <br>
<br>
+1 213 293 7889 <br>
<br>
Skype: dennisSchang <br>
<br>
<a moz-do-not-send="true" href="http://www.icann.org"
target="_blank" rel="noreferrer">www.icann.org</a> "One
World, One Internet" <br>
<br>
<br>
<br>
Links:<br>
------<br>
[1] <a moz-do-not-send="true"
href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en"
target="_blank" rel="noreferrer">https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en</a><br>
_______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt"
target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-impl-thickwhois-rt mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-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>