<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Could we replace GDPR by "applicable privacy regulations"? Seems
      to be more fitting as it takes into account that there is more
      than the GDPR out there.</p>
    <p>Best,</p>
    <p>Volke<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 28.08.2018 um 19:34 schrieb Lisa
      Phifer:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAAo-ce8czU7SixNogmzt8E7NLOTt3yTCm0vF7FFtu1xdB9CdtA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">Team,
        <div><br>
        </div>
        <div>On behalf of Alan, please be advised that the
          implementation timeframe for R3.1 has been clarified as
          follows.</div>
        <div><br>
        </div>
        <div>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
              class="gmail-BoldChar" style="font-weight:bold"><i>Implementation:</i></span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><i><s
                style="font-size:11pt">This recommendation should
                ideally be implemented post-GDPR implementation, but no
                later than [TBD months]
                after the recommendation is adopted.</s><span
                style="font-size:11pt"> The implementation should begin
                once
                it is moderately clear how GDPR will be addressed with
                relation to gTLD RDS
                (WHOIS). Should the implementation of this
                recommendation be deferred past
                FY2020, the then existing RDS (WHOIS)-related parts of
                the ICANN web site must
                be amended to cross-link the various sections on the RDS
                (WHOIS) portal, ICANN
                Contractual Compliance, Registrar and ICANN Learn.</span></i><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small">   </span><br>
          </p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small"><br>
            </span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small">During
              copy edits, it was noticed that the first sentence still
              contained a placeholder [TBD months] and could be seen as
              duplicating and perhaps even conflicting with the second
              sentence. To resolve this, Alan has proposed deleting the
              first sentence and letting the second sentence alone
              address implementation timeframe. </span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small"><br>
            </span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small">Because
              this is more substantive than a copy edit, Alan asked that
              the RT be advised of this change. </span><span
              style="font-family:Arial,Helvetica,sans-serif;font-size:small">Any
              objection to this change should be raised to the RT list
              ASAP but no later than 29 August 23.59 UTC.</span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small"><br>
            </span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small">Regards,</span></p>
          <p class="MsoNormal" style="text-align:justify;margin:0in 0in
            0.0001pt;font-size:11pt;font-family:Arial,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif;font-size:small">Lisa<br>
            </span></p>
        </div>
      </div>
      <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>