<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Alan,</p>
    <p>I see it in a similar way to the recommendations of the first RT.
      When the first RT recommended that ICANN make Whois a strategic
      priority, we can certainly do the same for safeguarding
      registration data in the context of data privacy laws. Years down
      the road, a new RT can then review how well ICANN did in that
      regard.</p>
    <p>I would also recommend that we reference this in our review of
      the stratprio recommendation as ICANN seems to have mainly ignored
      that aspect even though the recommendation read that it should
      make it a stratprio in ALL of its aspects. The rush and panic we
      are experiencing now is a direct result of this failure and we
      should not ignore this in our report. In fact, it may be the
      biggest issue ICANN has with the implementation of the first RT
      recs, depending on their interpretation, of course.<br>
    </p>
    <p>Volker<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 13.04.2018 um 18:49 schrieb Alan
      Greenberg:<br>
    </div>
    <blockquote type="cite"
cite="mid:YTXPR01MB0399E99FAA88E177E647390893B30@YTXPR01MB0399.CANPRD01.PROD.OUTLOOK.COM">I
      have no problem with noting this, but I see no actionable
      recommendation. The Board has already chartered a PDP and is
      taking
      interim (GDPR) corrective action.<br>
      <br>
      At 13/04/2018 12:38 PM, Volker Greimann wrote:<br>
      <br>
      <blockquote type="cite" class="cite" cite="">Not really, we should
        just
        analyze for how long ICANN has known about this issue but chosen
        to
        ignore it, and recommend that they now take the safeguarding of
        private
        data to heart and learn from past mistakes. We will not (and
        should not)
        give specific implementation advice or tell them how to do their
        job. But
        we can tell them that they should do their job and in fact
        should have
        done their jobs years ago. <br>
        <br>
        The how and what is ICANNs business and we should not intrude on
        that,
        but the fact that action and a re-orientation is needed is
        something that
        we very well can recommend. This will re-enforce the requirement
        but not
        intrude on any ongoing work.<br>
        <br>
        I believe this is one of the single most important issues
        regarding whois
        and by ignoring it we risk total irrelevance of our work. <br>
        <br>
        Volker<br>
        <br>
        Am 13.04.2018 um 17:31 schrieb Alan Greenberg:<br>
        <blockquote type="cite" class="cite" cite="">It is stating an
          opinion on how
          ICANN should be preceding. We have already agreed that we will
          say that
          the data has been completely open and that ICANN has provided
          NO
          protection against any use or abuse.<br>
          <br>
          If GDPR and the PDP were not happening, we could certainly
          make a
          recommendation that ICANN should charter a group to decide on
          what data
          should be protected and how. But that seems rather moot at
          this point in
          time.<br>
          <br>
          Alan<br>
          <br>
          At 13/04/2018 10:28 AM, Stephanie Perrin wrote:<br>
          <br>
          <blockquote type="cite" class="cite" cite=""><font size="1">How
              is Volkers
              suggestion getting us actively involved in the GDPR
              frenzy?  I think
              it is a logical thing to do.<br>
            </font><br>
            <font size="1">Stephanie</font><br>
            On 2018-04-13 10:17, Alan Greenberg wrote:<br>
            <blockquote type="cite" class="cite" cite="">Volker, we made
              a decision long
              ago to not get actively involved in the GDPR frenzy as
              that directly
              overlaps with the current process (as faulted as some
              people may think it
              is). Moreover, given the timing of our final report, it is
              not at all
              obvious what purpose such work would serve.<br>
              <br>
              Alan<br>
              <br>
              At 13/04/2018 07:12 AM, Volker Greimann wrote:<br>
              <br>
              <blockquote type="cite" class="cite" cite="">I think we
                should, under the
                shadow of the oncoming GDPR, expand on the analysis
                section under 3 a),
                stating that in this respect, ICANN and the community
                seem to have failed
                completely at ensuring registrant details are
                safeguarded from
                unauthorized or abusive access. We can then point to the
                extreme volumes
                of spam each new registration generates for the
                registrant, the
                harvesting of data in historic databases and various
                examples of doxxing
                (if we find any) based on whois data. <br>
                <br>
                This would then also inform the question we could ask
                not only contracted
                parties, but also affected members of civil society.<br>
                <br>
                Our summary of relevant research should also include
                every letter DPAs
                have ever written to ICANN on this topic, including the
                letter from the
                Dutch DPA Re: .Amsterdam.<br>
                <br>
                Volker<br>
                <br>
                Am 12.04.2018 um 21:48 schrieb Alan Greenberg:<br>
                <blockquote type="cite" class="cite" cite="">Attached
                  please find the updated
                  draft report and slide deck.<br>
                  <br>
                  At 10/04/2018 12:48 AM, Lisa Phifer wrote:<br>
                  <br>
                  <blockquote type="cite" class="cite" cite="">Dear
                    Subgroup 5 (Safeguarding
                    Registrant Data) -<br>
                    <br>
                    As discussed in our plenary call, attached are draft
                    slides for Alan to
                    review/revise on behalf of your subgroup.<br>
                    <br>
                    The content of these slides is based on this draft
                    subgroup report:<br>
                    <a
href="https://community.icann.org/download/attachments/71604740/Subgroup5-SafeguardData-Report-Draft1.docx"
                      eudora="autourl" moz-do-not-send="true">
https://community.icann.org/download/attachments/71604740/Subgroup5-SafeguardData-Report-Draft1.docx</a>
                    <br>
                    <br>
                    As a reminder, here is the timeline for slide
                    completion:<br>
                    • <b>Monday 9 April COB</b> - ICANN org support
                    team to send draft slides
                    to subgroup Rapporteurs <br>
                    • <b>Thursday 12 April COB</b> - Rapporteurs to
                    send final updates to
                    slides to ICANN org support team <br>
                    • <b>Friday 13 April COB</b> - ICANN org support
                    team to circulate final
                    slide-deck with the review team <br>
                    <br>
                    Regards<br>
                    Lisa<br>
                    Content-Type: application/octet-stream; name="RDS -
                    Brussels F2F MTG
                    - Draft Slides - SG5 DataSafe.pptx";<br>
                     x-mac-type="534C4433";
                    x-mac-creator="50505433"<br>
                    Content-Disposition: attachment; filename="RDS -
                    Brussels F2F MTG -
                    Draft Slides - SG5 DataSafe.pptx"<br>
                    X-Microsoft-Exchange-Diagnostics:<br>
                    <x-tab>        </x-tab>
1;YTOPR01MB0396;27:MqKo9F512hQvQz5+v4rhqfuD5de02Qc03fK6EZkp0jXxK1xa0k19wYA53bV1QNYrI07qWY1Q4+B1fgN0Qx7D5GNb75zzNpEMPrk1uNG291ewcsNg1R5F1ccqacMAJNbi<br>
                    X-Microsoft-Antispam-Message-Info:<br>
                    <x-tab>        </x-tab>
lWmLDC3W3a1iVEzM34JwpUSw3WWqVKn6AoVxKvtTY2isRYpV06AYdWdhg8OQHLYXYJJ0aEVpuTbIpoXW/pBSfmc5q6Tctzt1lS5Ud59u29EM1IVc+/3eWosPPiMW/mfRTjuq4StZdTOafUJjwf/vB7pnxHts9GQjmo9C7F0wW3yx5TbmKeRNkjG2+578NQvHKqtbmYNTaQuJuw/v9yevcJY67kez7190Trd0pYTJva1WQw+S2U7pW6vWlROut5sOEHRUeOeyp1t9cPi/ihnLpz0eLf1CEDo6yagGqtC4uUSL0QIJYEtmlgthYcvvAMt4NCZJUQMhq9Z0u0ASU9P2Yo1YhH7Sdn4sWc2/l3dRFwMbQshKgTx6dOCYisVWTqW3x7N4s4wBaNDodW9HsVu5eyeIvT+fUD8j3yJo+ukp/nQm47T9zJnOFqLuO15tmc/xw76p+ZBz/bJF9BJT0B9N/2mU7VpAUtteXX3VtLT2zoeZ/qf2837YJUJJ09H77WLj<br>
                    <br>
                    Content-Type: text/plain; charset="us-ascii"<br>
                    Content-Transfer-Encoding: 7bit<br>
                    Content-Disposition: inline<br>
                    X-Microsoft-Exchange-Diagnostics:<br>
                    <x-tab>        </x-tab>
1;YTOPR01MB0396;27:MqKo9F512hQvQz5+v4rhqfuD5de02Qc03fK6EZkp0jXxK1xa0k19wYA53bV1QNYrI07qWY1Q4+B1fgN0Qx7D5GNb75zzNpEMPrk1uNG291ewcsNg1R5F1ccqacMAJNbi<br>
                    X-Microsoft-Antispam-Message-Info:<br>
                    <x-tab>        </x-tab>
lWmLDC3W3a1iVEzM34JwpUSw3WWqVKn6AoVxKvtTY2isRYpV06AYdWdhg8OQHLYXYJJ0aEVpuTbIpoXW/pBSfmc5q6Tctzt1lS5Ud59u29EM1IVc+/3eWosPPiMW/mfRTjuq4StZdTOafUJjwf/vB7pnxHts9GQjmo9C7F0wW3yx5TbmKeRNkjG2+578NQvHKqtbmYNTaQuJuw/v9yevcJY67kez7190Trd0pYTJva1WQw+S2U7pW6vWlROut5sOEHRUeOeyp1t9cPi/ihnLpz0eLf1CEDo6yagGqtC4uUSL0QIJYEtmlgthYcvvAMt4NCZJUQMhq9Z0u0ASU9P2Yo1YhH7Sdn4sWc2/l3dRFwMbQshKgTx6dOCYisVWTqW3x7N4s4wBaNDodW9HsVu5eyeIvT+fUD8j3yJo+ukp/nQm47T9zJnOFqLuO15tmc/xw76p+ZBz/bJF9BJT0B9N/2mU7VpAUtteXX3VtLT2zoeZ/qf2837YJUJJ09H77WLj<br>
                    <br>
                    _______________________________________________<br>
                    RDS-WHOIS2-Safeguard mailing list<br>
                    <a href="mailto:RDS-WHOIS2-Safeguard@icann.org"
                      moz-do-not-send="true">
                      RDS-WHOIS2-Safeguard@icann.org</a><br>
                    <a
                      href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard"
                      eudora="autourl" moz-do-not-send="true">
https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
                  </blockquote>
                  <br>
                  <br>
                  <br>
                  <br>
                  <br>
                  <pre>_______________________________________________
RDS-WHOIS2-Safeguard mailing list
<a href="mailto:RDS-WHOIS2-Safeguard@icann.org" moz-do-not-send="true">
RDS-WHOIS2-Safeguard@icann.org</a>


<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard" eudora="autourl" moz-do-not-send="true">
https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
</pre>
                </blockquote>
                <br>
                <br>
                <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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl" moz-do-not-send="true">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> /


<a href="http://www.brandshelter.com/" eudora="autourl" moz-do-not-send="true">
www.BrandShelter.com</a>

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


<a href="http://www.facebook.com/KeySystems" eudora="autourl" moz-do-not-send="true">
www.facebook.com/KeySystems</a>


<a href="http://www.twitter.com/key_systems" eudora="autourl" moz-do-not-send="true">
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" moz-do-not-send="true">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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl" moz-do-not-send="true">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> /


<a href="http://www.brandshelter.com/" eudora="autourl" moz-do-not-send="true">
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" eudora="autourl" moz-do-not-send="true">
www.facebook.com/KeySystems</a>


<a href="http://www.twitter.com/key_systems" eudora="autourl" moz-do-not-send="true">
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" moz-do-not-send="true">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>
                <br>
                Content-Type: text/plain; charset="us-ascii"<br>
                Content-Transfer-Encoding: 7bit<br>
                Content-Disposition: inline<br>
                X-Microsoft-Exchange-Diagnostics:<br>
                <x-tab>        </x-tab>
1;YQBPR01MB0385;27:fcoqR4+uQx1cyGOa1rme9k1E26KN5BcsZFadOZrjuGKGe7AHjG/qCOF9GKny6kQC+sknDU0Rmt2EvTh31LI81uGQ5pnN+/OjCIM2R7AqiIlAB8NqeoYIRW0/N4vlidxs<br>
                X-Microsoft-Antispam-Message-Info:<br>
                <x-tab>        </x-tab>
h7DLEGRKssrWt0XZkpU/cfqfkvSlhNZtMdAXGyjy8SBORAWoYaHHuu540i/p+0P4N14ceih+Vh3gGPTomEuWyh0P/jWxWqoeuWrhXet+ZcT/6sBtjai5psejClJGel4KVCF9yjd1zBb5OGZOokf5YK66srrmyE/tDJkRC3DauI6kDTKDbzF6PZnBfJJT8GSYrbSyfNuBSJAMFcj/wtk5QDey8uURQM0POrYKjtbiEXBNUy4H56bfADX8GbwfHOTq1RoIW+j+v42CZCAouCy11Cx4dVDijO0Rj9urFmsbNl1tE8TFx0pNOko1fI36Dhg6O28qRqpUm6SCfRa/kCcd3qp7JTBxgLYlR5mKljhvihMXyscPfxQkULs2FRN7PCpAkNbswO0a7/06nfPwDVQTwqE4ej9vzp5sxw5FKJ1V+6GRlIZRgUOZB1ddGQRwKjGzLrFUfmZ5p9bf63FuoUiv9tVnLVtHRPafG8Tp4ZJCFhI/tdvLTQhivePjc+tGopaU<br>
                <br>
                _______________________________________________<br>
                RDS-WHOIS2-Safeguard mailing list<br>
                <a href="mailto:RDS-WHOIS2-Safeguard@icann.org"
                  moz-do-not-send="true">
                  RDS-WHOIS2-Safeguard@icann.org</a><br>
                <a
                  href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard"
                  eudora="autourl" moz-do-not-send="true">
https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
              </blockquote>
              <br>
              <br>
              <br>
              <pre>_______________________________________________
RDS-WHOIS2-Safeguard mailing list
<a href="mailto:RDS-WHOIS2-Safeguard@icann.org" moz-do-not-send="true">
RDS-WHOIS2-Safeguard@icann.org</a>

<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard" eudora="autourl" moz-do-not-send="true">
https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
</pre>
            </blockquote>
            Content-Type: text/plain;
            charset="us-ascii"<br>
            Content-Transfer-Encoding: 7bit<br>
            Content-Disposition: inline<br>
            X-Microsoft-Exchange-Diagnostics:<br>
            <x-tab>        </x-tab>
1;YQBPR01MB0385;27:TT8NPlVP+/IHoLBf2Ng0SLTFRHHQkQ+/HPYRgOcNmBrJlapLnNNJh7vOyeJ9Ar9/1xf8v5FIvXSMKbfqPtXpmmmfmM4eMGmhrrT6Zn9mY6XQHkQNfPtO9SZ1bFB8N0uS<br>
            X-Microsoft-Antispam-Message-Info:<br>
            <x-tab>        </x-tab>
6p3YdvBEEgNI70W8+jWVUX7dHQiCDN5xLjXjwkJ0br9PDWzEj8S9GNMyetpa0xF8Kycujd3DI33zJzKtQvC0MmAIlSGIIMk5zDpXcevqmxIDPkYeErQWMzwaHUK84SBr7bC6bZiOYCPD5UnTnAb4clYyTFNECyKq88uNg5xeE7meI4VCWpZJODJhKF9BYbWPR9VnFVeB5IR16PDhW+bwRqisxOO/5Zb3VB6aAErPcw+59iRtUvv5hiZ5qRR0o0D/KQPJn5b01CpAB3Ib3aaot0MfemUmjKQjF88vz3IysP41WwihuJYZd5vUziZJqIsqYYrrAaDN+BXjIjxqIved2ktxiJtUErq1FlJN0WAfKvGOPilPKvLA+UKf9S8u/qNOsiqpjzSQU56QOUP7T8IhLaXm7JMgsTXzG4tHSpQyNTL10nGGSi0PdgB2Dc9+cT1/tNEkXjyFk4KZP7xTgvYhnyQ1tDeXwW+r+bcS4k+GlhtC7IiV5AhU9HTxmtPPLQtl<br>
            <br>
            _______________________________________________<br>
            RDS-WHOIS2-Safeguard mailing list<br>
            <a href="mailto:RDS-WHOIS2-Safeguard@icann.org"
              moz-do-not-send="true">
              RDS-WHOIS2-Safeguard@icann.org</a><br>
            <a
              href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard"
              eudora="autourl" moz-do-not-send="true">
              https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
          </blockquote>
          <br>
          <br>
          <br>
          <pre>_______________________________________________
RDS-WHOIS2-Safeguard mailing list
<a href="mailto:RDS-WHOIS2-Safeguard@icann.org" moz-do-not-send="true">
RDS-WHOIS2-Safeguard@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard" eudora="autourl" moz-do-not-send="true">
https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl" moz-do-not-send="true">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" eudora="autourl" moz-do-not-send="true">
www.BrandShelter.com</a>

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a href="http://www.facebook.com/KeySystems" moz-do-not-send="true">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" eudora="autourl" moz-do-not-send="true">
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" moz-do-not-send="true">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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl" moz-do-not-send="true">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" eudora="autourl" moz-do-not-send="true">
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" moz-do-not-send="true">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" eudora="autourl" moz-do-not-send="true">
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" moz-do-not-send="true">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>
        Content-Type: text/plain; charset="us-ascii"<br>
        Content-Transfer-Encoding: 7bit<br>
        Content-Disposition: inline<br>
        X-Microsoft-Exchange-Diagnostics:<br>
        <x-tab>        </x-tab>
1;YQBPR01MB0385;27:yAq1iFP/95EuszjlQeP2HEv8q8p1/oIS2khTKinG+CgA7k4JoSDJ1eg9sg328rPlJwt4U6sMKSYciajcKtNCCH6aI1TFM66565Fwe2leKb8/RHSQyMp+6eX0exubP2Zf<br>
        X-Microsoft-Antispam-Message-Info:<br>
        <x-tab>        </x-tab>
NVdnEe4F4p+DmqCWNEOUt3rOchoVOZnV5+p5jW+04qscScrrVtn5fW24kdHWSKSM6n+Ip+ow/UgIU9RNb34Kf9lmtljibABVao70wl0+KIe96GContpGgZkVfNDCNJg0iHZWl9fGp6vTg0mLHfaLWrPlULPal5X9xAF/c/94ywBUVh39DM6PYOhI58x7GaWWKRGqFBSQ83GTl9IIbjQz4A6LrewnrPfhbToy02izDK8AbdPW+KzuYMqPp06Y9iiCfRLJw29Gdo0J8sEid6ZKUYcDSIH9ooIu5k6nSQWAcgBscy52fqM1gd4t4WkNkG0zhyh4G2m5HE5BwTgkgcLT74Xrk7UWfQobBQvU002Aly5ZcqaqdgE52+dBgES/LxE4Op9i1fFk+JemWz59601g8oE8OnL8AXCQ6NmiP3pTVfm3Zr2sQzfbuX0DPETGHzHkwhPgr6gBi54eonaxRuSjCz0YgppT3EqVTQwf6Isu+tzUN7RS+sSdIIgcotb6uNg0<br>
        <br>
        _______________________________________________<br>
        RDS-WHOIS2-Safeguard mailing list<br>
        <a class="moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-Safeguard@icann.org">RDS-WHOIS2-Safeguard@icann.org</a><br>
        <a
          href="https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard"
          eudora="autourl" moz-do-not-send="true">
          https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard</a>
      </blockquote>
    </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>