<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">One analyst says there are at least 40+ areas in the GDPR that could be modified/interpreted by national law and regulations. Which is why they say if Schrems prevails in his lawsuits, we may very well see a reduction in the surface area for [re]interpretation.</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">Almost 20 years ago, I was sent to a workshop [sponsored by a U.S. regulator!] on regulatory intent. The takeaway that remains top of mind even today was this old guy advising us to become English language specialists for a successful career writing or interpreting regulations; definitions matters most, he said. Lo and behold, I see this advice validated every day since. </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">IMHO, the thing seemingly most overlooked is the definition of 'data subject' and how that plays out in a practical way. That definition makes individuals the subject of data, never mind whether they are inside EU borders or not. Maybe it is serendipity that the idea is connected to a fact of our digital lives; digital data can be anywhere and everywhere at one, effectively loosening it bindings to territory. This is the kernel of the extraterritorial reach of the law. </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<br></div></div><div class="gmail_extra"><br clear="all"><div><div 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 class="gmail_quote">On Wed, May 30, 2018 at 11:27 AM, Volker Greimann <span dir="ltr"><<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  <div text="#000000" bgcolor="#FFFFFF">

    <p>One thing that every critic gets wrong is that in most European

      legislation, the vagueness is intentional and regulations and laws

      are much more reliant on interpretation. This allows for a broader

      cover than specific language, but also for more diverse ways of

      interpretation. In effect, those tasked with implementation are a

      lot freer in how to do so. <br>

    </p>

    <p>Best <br><span class="HOEnZb"><font color="#888888">

    </font></span></p><span class="HOEnZb"><font color="#888888">

    <p>Volker<br>

    </p></font></span><div><div class="h5">

    <br>

    <div class="m_2997645921864117899moz-cite-prefix">Am 30.05.2018 um 17:59 schrieb Chris

      Disspain:<br>

    </div>

    <blockquote type="cite">

      Seems like it’s not just ‘ICANN’ that is not a fan of GDPR...<br>

      <br>

      <div>Cheers,

        <div><br>

        </div>

        <div>Chris</div>

        <div><br>

        </div>

      </div>

      <div>

        <blockquote type="cite">

          <div class="m_2997645921864117899WordSection1">

            <h1 style="margin-right:0in;margin-left:0in;margin-bottom:15pt;line-height:24pt"><font color="#000000"><span style="font-size:16px;background-color:rgba(255,255,255,0)"><span class="m_2997645921864117899article-classifiergap"><span lang="EN-GB">EU data privacy laws are likely to

                      create barriers to trade</span></span><span lang="EN-GB"></span><u></u><u></u></span></font></h1>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt;line-height:18pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"><span lang="EN-GB">GDPR

                    creates serious, unclear legal obligations for both

                    private and public entities</span><u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"><span lang="EN-GB"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ft.com_stream_c282e9be-2Dedd9-2D3de8-2D8b0c-2De697dd30c800&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=W6FGoh-o78gkKZN3_sXelY30VwoSX288Wo9XnUkQrK8&m=VfOhFAsJy97RwESrvrnrTSkhx0uJWaGvNSqGXGumqxQ&s=56fGyMUXCEaAk52abfL-oQIioE_ZnquZH-AW2j9iMIg&e=" target="_blank">WILBUR ROSS [FT.COM]</a></span><u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">We in the

                  US are deeply concerned about the way the EU’s new

                  privacy guidelines, which came into effect last week,

                  will force big changes in the way US and European

                  companies do business.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">Donald

                  Trump’s administration supports the new General Data

                  Protection Regulation’s goal of protecting personal

                  online data while continuing to enable transatlantic

                  data exchange.  We are also committed to working with

                  the EU to implement the new guidelines.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">We believe

                  that data-sharing rules must respect privacy and

                  protect our shared interests of maintaining public

                  safety and the easy functioning of the internet, while

                  also taking into account the regulatory, scientific,

                  and commercial needs of all our countries. As

                  currently envisioned, GDPR’s implementation could

                  significantly interrupt transatlantic co-operation and

                  create unnecessary barriers to trade, not only for the

                  US, but for everyone outside the EU.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">The US

                  thrives because it has an open, entrepreneurial

                  society that encourages innovation and embraces

                  technological advances. We believe consumers benefit

                  because they enjoy the digital products and services

                  that are invented and brought to market by US

                  companies. <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">Complying

                  with GDPR will exact a significant cost, particularly

                  for small and medium-sized enterprises and consumers

                  who rely on digital services and may lose access and

                  choice as a result of the guidelines. US companies

                  have already invested billions of dollars to comply

                  with the new rules. But even as companies update their

                  privacy policies to bring themselves in line, many

                  uncertainties remain.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">GDPR

                  creates serious, unclear legal obligations for both

                  private and public sector entities, including the US

                  government. We do not have a clear understanding of

                  what is required to comply. That could disrupt

                  transatlantic co-operation on financial regulation,

                  medical research, emergency management co-ordination,

                  and important commerce. It could threaten public

                  welfare on both sides of the Atlantic. US and European

                  financial services regulators may be impeded from

                  carrying out important activities: for example, it is

                  unclear whether EU supervisors can share information

                  with the US for compliance exams and other oversight.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">Pharmaceutical

                  companies may not be able to submit medical data from

                  drug trials involving European patients to US

                  authorities, which could delay the approval of new

                  life-saving drugs. The Centers for Disease Control and

                  Prevention could be restricted in sharing information

                  with European counterparts while responding to the

                  outbreak of diseases such as Ebola. And the US Postal

                  Service believes the new rules will prevent EU postal

                  operators from providing the personal data on

                  individuals it needs to process inbound mail. <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">GDPR also

                  raises concern for law enforcement and intellectual

                  property rights by restricting access to publicly

                  available internet domain-name registration data. We

                  anticipate companies will either stop providing

                  “Whois” look-up services outright, or make it hard to

                  access the information. That could stop law

                  enforcement from ascertaining who is behind websites

                  that propagate terrorist information, sponsor

                  malicious botnets or steal IP addresses.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">These

                  important activities need to be weighed carefully

                  against privacy concerns. They are critical to

                  building trust in the internet, safeguarding

                  infrastructure, and protecting the public. Our respect

                  for privacy does not have to come at the expense of

                  public safety. <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">We must

                  find a way to implement GDPR without creating undue

                  barriers. Privacy is an important and timely issue,

                  but it also is a complex one. The guidance on GDPR

                  implementation is too vague. EU authorities must

                  provide clearer rules and a more predictable

                  regulatory environment to support investment and

                  innovation. We ask them to act quickly so that GDPR

                  can be properly implemented.<u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> <u></u><u></u></span></font></p>

            <p class="MsoNormal" style="margin:0in 0in 0.0001pt"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">The writer

                  is the US commerce secretary</span></font></p>

          </div>

        </blockquote>

      </div>

      <div><br>

        On 30 May 2018, at 15:45, Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com" target="_blank">carlton.samuels@gmail.com</a>>

        wrote:<br>

        <br>

      </div>

      <blockquote type="cite">

        <div>

          <div dir="ltr">

            <div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">I

              read the pleading eventually and in fairness to Jones Day,

              they threw everything they got into their filing, the baby

              and bathwater included.  So naturally the overreach on

              trademark and content regulation that Milton and them

              getting excited about made its way there.</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">Comparing

              the arguments presented to the directives of the GDPR,

              self defeat seems evident. So maybe it is a fiendishly

              clever legal strategy at play and this is a test case to

              get a few markers down for the big one. But from the

              pleadings of facts and intended outcome, this one, IMHO,

              is as weak as a strain of denatured bacteria. </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 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"><br>

            </div>

          </div>

          <div class="gmail_extra"><br clear="all">

            <div>

              <div class="m_2997645921864117899gmail_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 class="gmail_quote">On Wed, May 30, 2018 at 7:21 AM,

              Volker Greimann <span dir="ltr"><<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>></span>

              wrote:<br>

              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

                <div text="#000000" bgcolor="#FFFFFF"> Of course he

                  will. ICANN has been acting ill-advised from the

                  start. Instead of embracing GDPR and its impact and

                  taking the essence of the regulation at heart and

                  building upon that basis, ICANN ORG (and parts of the

                  community) has been shirking its responsibilites until

                  this day and continued to search for loopholes,

                  excemptions and ways around it. <br>

                  <br>

                  The law suit is just the latest example of this

                  painful process, where ICANN now is specifically

                  expanding its mandate to define a purpose for the

                  collection of certain data.<br>

                  <br>

                  Some excellent reading material on this issue can be

                  found here:<br>

                  <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-freetext" href="https://www.internetgovernance.org/2018/05/28/the-injunction-icanns-lame-attempt-to-turn-dns-into-a-trademark-registry/" target="_blank">https://www.internetgovernance<wbr>.org/2018/05/28/the-<wbr>injunction-icanns-lame-<wbr>attempt-to-turn-dns-into-a-<wbr>trademark-registry/</a><br>

                  <br>

                  Best,<br>

                  Volker<span><br>

                    <div class="m_2997645921864117899m_4173234067177970604moz-cite-prefix"><br>

                    </div>

                    <blockquote type="cite">

                      <div dir="ltr"><br>

                        <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">I

                          have a feeling Schrems will likely triumph

                          before ICANN.</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 class="gmail_extra"><br clear="all">

                        <div>

                          <div class="m_2997645921864117899m_4173234067177970604gmail_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 class="gmail_quote">On Sun, May 27, 2018 at

                          11:05 PM, Alan Greenberg <span dir="ltr"><<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>></span>

                          wrote:<br>

                          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://www.icann.org/news/announcement-2018-05-25-en" rel="noreferrer" target="_blank">https://www.icann.org/news/ann<wbr>ouncement-2018-05-25-en</a><br>

                            <br>

                            For those who might not have noticed, on

                            Friday, ICANN announced that it has filed

                            injunction proceedings against a German

                            registrar (associated with TUCOWS) that had

                            informed ICANN that under the GDPR, it would

                            no longer be collecting certain data (Admin

                            and Technical contact info).<br>

                            <br>

                            Collection is a critical step, in that if

                            data is not collected, it cannot be released

                            to accredited parties, no matter how good

                            their justification is.<br>

                            <br>

                            As I understand it (and that could be

                            wrong), this is an interesting step, in that

                            it takes the issue out of the hands of data

                            commissioners and into the courts, where

                            presumably ICANN will be given an

                            opportunity to explain why it believes that

                            such collection is important. Although data

                            commissioners have been reported to say that

                            they have no legal basis to grant a delay,

                            this is something that the courts can do

                            pending resolution.<br>

                            <br>

                            Alan<br>

                            <br>

                            ______________________________<wbr>_________________<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/l<wbr>istinfo/rds-whois2-rt</a><br>

                          </blockquote>

                        </div>

                        <br>

                      </div>

                      <br>

                      <fieldset class="m_2997645921864117899m_4173234067177970604mimeAttachmentHeader"></fieldset>

                      <br>

                      <pre>______________________________<wbr>_________________

RDS-WHOIS2-RT mailing list

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a>

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/rds-whois2-rt</a>

</pre>

                    </blockquote>

                    <br>

                  </span>

                  <pre class="m_2997645921864117899m_4173234067177970604moz-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="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" 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 class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" 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.

------------------------------<wbr>--------------

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="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" 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 class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>

<a class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" 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 class="m_2997645921864117899m_4173234067177970604moz-txt-link-abbreviated" 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>

                </div>

                <br>

                ______________________________<wbr>_________________<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/l<wbr>istinfo/rds-whois2-rt</a><br>

                <br>

              </blockquote>

            </div>

            <br>

          </div>

        </div>

      </blockquote>

      <blockquote type="cite">

        <div><span>______________________________<wbr>_________________</span><br>

          <span>RDS-WHOIS2-RT mailing list</span><br>

          <span><a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a></span><br>

          <span><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/rds-whois2-rt</a></span><br>

        </div>

      </blockquote>

      <br>

      <fieldset class="m_2997645921864117899mimeAttachmentHeader"></fieldset>

      <br>

      <pre>______________________________<wbr>_________________

RDS-WHOIS2-RT mailing list

<a class="m_2997645921864117899moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a>

<a class="m_2997645921864117899moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/rds-whois2-rt</a>

</pre>

    </blockquote>

    <br>

    <pre class="m_2997645921864117899moz-signature" cols="72">-- 