<div dir="ltr">[volker&#39;s email]<div>&gt;&gt;We are not talking about twitter, facebook, gmail,or any other service. We are talking about domain registrations. And on all those services I can chose how much of my private details I want to share and with whom. </div><div><br></div><div>Simple yes or no question for you. Did you forget that whois privacy protect features exist?</div><div><br></div><div>[volker&#39;s email]<br></div><div>&gt;&gt;This is about storing the data after it has fulfilled its purpose, not about that data being out there at all. If I chose to publish my home IP on twiter, that is my choice. But I do not have to. There is no public twitter whois, no public email whois and no public facebook whois.<br></div><div><br></div><div>On social media it&#39;s not called whois it&#39;s called a profile page. And this isn&#39;t the working group about dictating-what-people-do-with-data-after-they-collect-it. </div><div><br></div><div>[volker&#39;s email]<br></div><div>&gt;&gt;things may be different in the US, but over here, when I buy a car, I do not get any spam from insurance companies. And I recently bought a house and I got not a single mail or contact request from someone I have not previously solicited for that. Yet for my new domain name, the counter now stands at 20 directly attributable spam messages in four days since the registration. <br></div><div><br></div><div>And how much spam did you get on your main email address and other emails that are not used for whois? If you want to talk statistics, then you&#39;re borderline trolling if you blow one number out of proportion while ignoring all the other sources of spam. I got 20 pieces of spam this morning. No one in good faith can use numbers that small to justify nuking an entire piece of internet infrastructure. </div><div><br></div><div><br></div><div>[volker&#39;s email]<br></div><div>&gt;&gt;things may be different in the US, but over here, when I buy a car, I do not get any spam from insurance companies. And I recently bought a house and I got not a single mail or contact request from someone I have not previously solicited for that. Yet for my new domain name, the counter now stands at 20 directly attributable spam messages in four days since the registration. <br></div><div><br></div><div>And that has nothing to do with a lack of data collection. It is entirely related to penalties that these companies will face if they contact you outside the bounds of what is legal. Keeping regularly-used contact information secret is a tried-and-failed method of preventing spam. The solution, time and again, has been to filter and to go after the spammers legally and criminally. you are trolling.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 29, 2017 at 4:39 AM, Volker Greimann <span dir="ltr">&lt;<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>&gt;</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>We are not talking about twitter, facebook, gmail,or any other
      service. We are talking about domain registrations. And on all
      those services I can chose how much of my private details I want
      to share and with whom. <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_-4716820262215756001moz-cite-prefix">Am 28.09.2017 um 19:26 schrieb John
      Bambenek via gnso-rds-pdp-wg:<br>
    </div>
    <blockquote type="cite">
      
      <p>Such laws ALREADY exist or there would be no twitter, facebook,
        gmail, or for that matter, almost any service we use on the
        internet.</p>
      <p>You have a Facebook account, I can datamine that all day if I
        want and not run into one iota of a problem with GDPR.<br>
      </p>
      <br>
      <div class="m_-4716820262215756001moz-cite-prefix">On 9/28/2017 11:09 AM, Volker
        Greimann wrote:<br>
      </div>
      <blockquote type="cite">
        
        <p>Then please start lobbying to the worlds&#39; governments to make
          laws that permit this use of personal data.</p>
        <p>Volker<br>
        </p>
        <br>
        <div class="m_-4716820262215756001moz-cite-prefix">Am 28.09.2017 um 15:50 schrieb John
          Bambenek via gnso-rds-pdp-wg:<br>
        </div>
        <blockquote type="cite">
          
          <div>Which is why whois privacy should be free for consumers
            which let&#39;s THEM make the decision what is sensitive and not
            US decide what is the norm for the entire planet for them. </div>
          <div id="m_-4716820262215756001AppleMailSignature"><br>
          </div>
          <div id="m_-4716820262215756001AppleMailSignature">I am unclear as to why this is an
            unsatisfactory answer. <br>
            <br>
            --
            <div>John Bambenek</div>
          </div>
          <div><br>
            On Sep 28, 2017, at 08:36, Stephanie Perrin &lt;<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.<wbr>utoronto.ca</a>&gt;
            wrote:<br>
            <br>
          </div>
          <blockquote type="cite">
            <div>
              
              <p><font size="+1"><font face="Lucida Grande">Making
                    sensitive data public does not, by legal definition,
                    change its character as personal data.</font></font></p>
              <p><font size="+1"><font face="Lucida Grande">Stephanie P</font></font><br>
              </p>
              <br>
              <div class="m_-4716820262215756001moz-cite-prefix">On 2017-09-28 09:34, John
                Bambenek via gnso-rds-pdp-wg wrote:<br>
              </div>
              <blockquote type="cite">
                
                <div>Public data cannot, by definition, be breached. </div>
                <div id="m_-4716820262215756001AppleMailSignature"><br>
                </div>
                <div id="m_-4716820262215756001AppleMailSignature">J<br>
                  <br>
                  --
                  <div>John Bambenek</div>
                </div>
                <div><br>
                  On Sep 28, 2017, at 08:29, theo geurts &lt;<a href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>&gt;
                  wrote:<br>
                  <br>
                </div>
                <blockquote type="cite">
                  <div> Indeed privacy prevents a lot of consumers being
                    exploited.<br>
                    <br>
                    Privacy by design usually plays a significant role
                    when setting up security around databases. Often,
                    less is more, data that is not present cannot cause
                    a data breach. The GDPR had to set a whole bunch of
                    rules around data breaches and response times and
                    accounting. Though given the number of weekly data
                    breaches, most likely for the best, yet it is still
                    a load of rules to deal with. <br>
                    <br>
                    Theo<br>
                    <br>
                    <div class="m_-4716820262215756001moz-cite-prefix">On 28-9-2017 15:19,
                      John Bambenek via gnso-rds-pdp-wg wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div>Thankfully there are people who donate their
                        time and talent tackling the privacy and
                        security risks that are seeking to exploit
                        consumers. ;)<br>
                        <br>
                        --
                        <div>John Bambenek</div>
                      </div>
                      <div><br>
                        On Sep 28, 2017, at 03:08, Volker Greimann &lt;<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>&gt;
                        wrote:<br>
                        <br>
                      </div>
                      <blockquote type="cite">
                        <div>
                          <p>The role of ICANN to ensure the stability
                            and security of the internet is a technical
                            role, not one of being an internet
                            policeman. That role is already filled by
                            internet policemen.</p>
                          <p>Volker<br>
                          </p>
                          <br>
                          <div class="m_-4716820262215756001moz-cite-prefix">Am 27.09.2017 um
                            20:05 schrieb Chuck:<br>
                          </div>
                          <blockquote type="cite">
                            
                            
                            <div class="m_-4716820262215756001WordSection1">
                              <p class="MsoNormal"><span style="color:windowtext">Without at
                                  all minimizing ICANN’s role with
                                  regard to security and stability of
                                  the Internet because I do believe that
                                  is a critical role, I do want to point
                                  out that that also is a limited role. 
                                  Here is a copy of the first part of
                                  ICANN’s mission from its Bylaws:</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="color:windowtext"> </span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="color:windowtext">“</span><span style="font-size:12.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">Section 1.1. MISSION</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">(a) The mission of the
                                  Internet Corporation for Assigned
                                  Names and Numbers (&quot;<b>ICANN</b>&quot;) is
                                  to ensure the stable and secure
                                  operation of the Internet&#39;s unique
                                  identifier systems as described in
                                  this <u>Section 1.1(a)</u> (the &quot;<b>Mission</b>&quot;).
                                  Specifically, ICANN:</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">(i) Coordinates the
                                  allocation and assignment of names in
                                  the root zone of the Domain Name
                                  System (&quot;<b>DNS</b>&quot;) and coordinates
                                  the development and implementation of
                                  policies concerning the registration
                                  of second-level domain names in
                                  generic top-level domains (&quot;<b>gTLDs</b>&quot;).
                                  In this role, ICANN&#39;s scope is to
                                  coordinate the development and
                                  implementation of policies:</span><u></u><u></u></p>
                              <p class="MsoNormal" style="margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span>         </span></span></span><span style="font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">For which uniform or
                                  coordinated resolution is reasonably
                                  necessary to facilitate the openness,
                                  interoperability, resilience, security
                                  and/or stability of the DNS including,
                                  with respect to gTLD registrars and
                                  registries, policies in the areas
                                  described in Annex G-1 and Annex G-2;
                                  and</span><u></u><u></u></p>
                              <p class="MsoNormal" style="margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt"><span style="font-size:10.0pt;font-family:Symbol"><span>·<span>         </span></span></span><span style="font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">That are developed through a
                                  bottom-up consensus-based
                                  multistakeholder process and designed
                                  to ensure the stable and secure
                                  operation of the Internet&#39;s unique
                                  names systems.</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">The issues, policies,
                                  procedures, and principles addressed
                                  in Annex G-1 and Annex G-2 with
                                  respect to gTLD registrars and
                                  registries shall be deemed to be
                                  within ICANN&#39;s Mission.</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">. . .</span><span style="color:windowtext">”</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">Note in (a) and the second
                                  bullet under (i) that it says “</span><span style="font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">to ensure the stable and
                                  secure operation of the Internet&#39;s
                                  unique identifier systems</span><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">”.  ICANN’s security and
                                  stability role is limited to its
                                  responsibilities involving the ‘</span><span style="font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">Internet&#39;s unique identifier
                                  systems</span><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN">’.  I am pretty sure
                                  everyone understands that but wanted
                                  to make sure.  For our purposes in
                                  this WG, ICANN has a clear mandate to
                                  ensure security and stability of the
                                  generic domain names system.</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333" lang="EN"> Chuck</span><u></u><u></u></p>
                              <p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p>
                              <p class="MsoNormal"><a name="m_-4716820262215756001__MailEndCompose"><span style="color:windowtext"><u></u> <u></u></span></a></p>
                              <span></span>
                              <div>
                                <div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
                                  <p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a>
                                      [<a class="m_-4716820262215756001moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>]
                                      <b>On Behalf Of </b>John Bambenek
                                      via gnso-rds-pdp-wg<br>
                                      <b>Sent:</b> Wednesday, September
                                      27, 2017 9:12 AM<br>
                                      <b>To:</b> <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
                                      <b>Subject:</b> Re:
                                      [gnso-rds-pdp-wg] ICANN
                                      Meetings/Conversations with Data
                                      Protection and Privacy
                                      Commissioners<u></u><u></u></span></p>
                                </div>
                              </div>
                              <p class="MsoNormal"><u></u> <u></u></p>
                              <p>Except that the domain name system is
                                not YOUR system, it is ICANN&#39;s who has a
                                very clear mandate for the security and
                                stability of the internet.<u></u><u></u></p>
                              <p>The purpose is NOT letting registrants
                                get domains and helping registries get
                                paid. It never has been.<u></u><u></u></p>
                              <p class="MsoNormal"><u></u> <u></u></p>
                              <div>
                                <p class="MsoNormal">On 09/27/2017 09:52
                                  AM, Volker Greimann wrote:<u></u><u></u></p>
                              </div>
                              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                                <p>Hi Greg,<u></u><u></u></p>
                                <p>I think we need to dig down even
                                  deeper initially. Instead of RDS, the
                                  core of the matter is the need for the
                                  data when defining the purpose for
                                  collection.<u></u><u></u></p>
                                <p>This is very easy to answer for
                                  registrars: &quot;We need (certain elements
                                  of) the data to be able to properly
                                  provide the business, invoice the
                                  customer, collect his payments, send
                                  reminders and notices, protect the
                                  rights of the customers in case of
                                  business failure, comply with legal
                                  requirements like record-keeping,
                                  etc.&quot;. I am leaving out any
                                  contractual requirements, as they do
                                  not matter for the registrars&#39; own
                                  purpose. These are external purposes
                                  that the registrar would have to
                                  execute without having an own, direct
                                  need for. <u></u><u></u></p>
                                <p>For registries, it gets fuzzier as
                                  they do not have a direct connection
                                  to the registrants. From a service
                                  provision perspective, registries have
                                  no need for the data, and no right to
                                  it, except maybe for purposes of
                                  eligibility verification. <u></u><u></u></p>
                                <p>When going beyond registries to the
                                  general public, there is no purpose
                                  that connects to the provision of the
                                  service to the registrant directly.
                                  There also (in most countries) is no
                                  legal requirement to collect and
                                  publish this data. Yet there is still
                                  a need for the data, as we have
                                  discussed in great detail. <u></u><u></u></p>
                                <p>So our first question always must be
                                  the following:<u></u><u></u></p>
                                <p>&quot;How do we serve the needs of the
                                  general public that has an interest in
                                  the ability of obtaining such data
                                  without violating any applicable laws
                                  or the rights of the registrant to the
                                  privacy of his data?&quot;<u></u><u></u></p>
                                <p>This has to be the basis of any
                                  design decision and any argument made
                                  in this group. <u></u><u></u></p>
                                <p>Arguing that certain laws are
                                  unreasonable or unworkable is a
                                  dangerous question as it effectively
                                  proposes to ignore laws that we as a
                                  community do not like, at the risk of
                                  contracted parties and to the
                                  detriment of the beneficiaries of such
                                  laws. just because there has not been
                                  any enforcement action in the past
                                  does not mean we can ignore the law
                                  applicable to the individual
                                  contracted parties. And we are not
                                  talking about jaywalking here, some of
                                  these laws have significant penalties
                                  attached to them, as we have also
                                  discussed before.  <u></u><u></u></p>
                                <p>I agree with Greg that the ability of
                                  contracted parties to be free to make
                                  business decisions cannot be absolute.
                                  It has to be bound on the one side by
                                  ICANN policies and the other side by
                                  applicable law. And these two external
                                  pressures should not be in conflict
                                  with each other. If we can achieve
                                  that while answering the basic
                                  question above, our work is done. At
                                  least for the time being, as laws may
                                  obviously change, but that can be
                                  taken into account as well. Any
                                  discussion that seeks to circumvent
                                  this basic question will ultimately
                                  lead to the failure of our work and by
                                  extention to the end of whois. The
                                  latter due to the incompatibility of
                                  current whois with applicable law.<u></u><u></u></p>
                                <p>I think with our initial &quot;purpose
                                  definition&quot; exercise, we already went
                                  a great way in determining what those
                                  needs are and our current work to
                                  discuss data points goes into that
                                  question as well, even though
                                  personally I feel that by defining
                                  data points at this point and going
                                  into the sticks in some of the
                                  discussions we are wasting time. The
                                  question should never be &quot;Do we need a
                                  Facebook contact in the RDS?&quot; and
                                  always be &quot;What contacts are needed as
                                  bare minimum to achieve needs X, Y, Z,
                                  ...&quot;. <u></u><u></u></p>
                                <p>Best,<u></u><u></u></p>
                                <p>Volker<u></u><u></u></p>
                                <p class="MsoNormal"><u></u> <u></u></p>
                                <div>
                                  <p class="MsoNormal">Am 27.09.2017 um
                                    16:00 schrieb Greg Shatan:<u></u><u></u></p>
                                </div>
                                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                                  <div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Arial&quot;,sans-serif">​</span><span style="font-family:&quot;Verdana&quot;,sans-serif">The &quot;data
                                          controllers&quot; here do not exist
                                          in a vacuum.  While registrars
                                          and registries need to be free
                                          to make many types of
                                          decisions in their own
                                          business judgment, that cannot
                                          be an absolute rule.  This is
                                          at odds with the ICANN model,
                                          consensus policy, etc.  In
                                          this case, the data
                                          controllers are part of a
                                          larger ecosystem, and the
                                          &quot;needs&quot; go beyond the
                                          individual business needs of
                                          each data controller. (Indeed,
                                          the individual data controller
                                          has its own database of
                                          information for its business
                                          needs.)<u></u><u></u></span></p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Verdana&quot;,sans-serif"><u></u> <u></u></span></p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Verdana&quot;,sans-serif">As
                                          I previously noted, we are
                                          going back to first principles
                                          -- which is not necessarily a
                                          bad thing.  Why does ICANN
                                          (and by extension, the
                                          Internet) need WHOIS/RDS? 
                                          That is the question.  Not
                                          &quot;why does a particular
                                          [registrar/registry] need
                                          WHOIS/RDS?&quot;<u></u><u></u></span></p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Verdana&quot;,sans-serif"><u></u> <u></u></span></p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Verdana&quot;,sans-serif">Greg</span><span style="font-family:&quot;Arial&quot;,sans-serif">​</span><span style="font-family:&quot;Verdana&quot;,sans-serif"><u></u><u></u></span></p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal"><span style="font-family:&quot;Verdana&quot;,sans-serif"><u></u> <u></u></span></p>
                                    </div>
                                  </div>
                                  <div>
                                    <p class="MsoNormal"><u></u> <u></u></p>
                                    <div>
                                      <p class="MsoNormal">On Wed, Sep
                                        27, 2017 at 5:12 AM, Volker
                                        Greimann &lt;<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>&gt;
                                        wrote:<u></u><u></u></p>
                                      <blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
                                        <div>
                                          <p>So when will you start
                                            advocating the collection
                                            and publication of WHOIS for
                                            internet users? Because they
                                            would be connecting to your
                                            network all the time...<u></u><u></u></p>
                                          <p><span style="color:#888888">Volker<u></u><u></u></span></p>
                                          <div>
                                            <div>
                                              <p class="MsoNormal"><u></u> <u></u></p>
                                              <div>
                                                <p class="MsoNormal">Am
                                                  26.09.2017 um 20:48
                                                  schrieb John Bambenek
                                                  via gnso-rds-pdp-wg:<u></u><u></u></p>
                                              </div>
                                            </div>
                                          </div>
                                          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                                            <div>
                                              <div>
                                                <p>&quot;<span>As
                                                    for privacy proxy
                                                    solving the problem,
                                                    it does not.  Over
                                                    collection is not
                                                    solved by providing
                                                    a proxy in the third
                                                    party disclosure
                                                    mechanism.  It is
                                                    still
                                                    over-collection,
                                                    disproportionate to
                                                    needs.&quot;</span><u></u><u></u></p>
                                                <p><span>I
                                                    fundamentally
                                                    disagree because the
                                                    purpose of ICANN is
                                                    not the mere
                                                    facilitation of
                                                    domain from registry
                                                    to registrant. The
                                                    purpose is the
                                                    security and
                                                    stability of the
                                                    internet and that
                                                    means I have a need
                                                    to verify who is
                                                    connecting to my
                                                    network and have a
                                                    means of contacting
                                                    them. That point has
                                                    never been made, to
                                                    my knowledge, to
                                                    them.</span><u></u><u></u></p>
                                                <p><span>The
                                                    point that removing
                                                    that ability of me
                                                    being able to
                                                    contact domain
                                                    owners does far MORE
                                                    to REDUCE the
                                                    privacy of the
                                                    registrants than
                                                    does publishing said
                                                    information.  We
                                                    talk often about
                                                    verification
                                                    out-of-band for
                                                    sensitive
                                                    communications. How
                                                    can I do that
                                                    without a phone
                                                    number?</span><u></u><u></u></p>
                                                <p><span>I
                                                    will loudly and
                                                    vigorously argue
                                                    that the path
                                                    advocated will make
                                                    the problem FAR
                                                    worse and not
                                                    better. Hopefully we
                                                    don&#39;t get to the
                                                    point where I have
                                                    actual data to prove
                                                    that.</span><u></u><u></u></p>
                                                <p class="MsoNormal"><u></u> <u></u></p>
                                                <div>
                                                  <p class="MsoNormal">On
                                                    9/26/2017 1:34 PM,
                                                    Stephanie Perrin
                                                    wrote:<u></u><u></u></p>
                                                </div>
                                                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                                                  <p class="MsoNormal"><span style="font-size:13.5pt;font-family:&quot;Lucida Grande&quot;,serif">As
                                                      for privacy proxy
                                                      solving the
                                                      problem, it does
                                                      not.  Over
                                                      collection is not
                                                      solved by
                                                      providing a proxy
                                                      in the third party
                                                      disclosure
                                                      mechanism.  It is
                                                      still
                                                      over-collection,
                                                      disproportionate
                                                      to needs.</span><u></u><u></u></p>
                                                </blockquote>
                                                <p class="MsoNormal"><br>
                                                  <br>
                                                  <u></u><u></u></p>
                                                <pre>-- <u></u><u></u></pre>
                                                <pre>--<u></u><u></u></pre>
                                                <pre><u></u> <u></u></pre>
                                                <pre>John Bambenek<u></u><u></u></pre>
                                                <p class="MsoNormal"><br>
                                                  <br>
                                                  <u></u><u></u></p>
                                              </div>
                                            </div>
                                            <pre>______________________________<wbr>_________________<u></u><u></u></pre>
                                            <pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
                                            <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
                                            <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
                                          </blockquote>
                                          <div>
                                            <div>
                                              <pre>-- <u></u><u></u></pre>
                                              <pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Mit freundlichen Grüßen,<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Volker A. Greimann<u></u><u></u></pre>
                                              <pre>- Rechtsabteilung -<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Key-Systems GmbH<u></u><u></u></pre>
                                              <pre>Im Oberen Werk 1<u></u><u></u></pre>
                                              <pre>66386 St. Ingbert<u></u><u></u></pre>
                                              <pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><u></u><u></u></pre>
                                              <pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><u></u><u></u></pre>
                                              <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><u></u><u></u></pre>
                                              <pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<u></u><u></u></pre>
                                              <pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><u></u><u></u></pre>
                                              <pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Geschäftsführer: Alexander Siffrin<u></u><u></u></pre>
                                              <pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <u></u><u></u></pre>
                                              <pre>Umsatzsteuer ID.: DE211006534<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Member of the KEYDRIVE GROUP<u></u><u></u></pre>
                                              <pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>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.<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>------------------------------<wbr>--------------<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Should you have any further questions, please do not hesitate to contact us.<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Best regards,<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Volker A. Greimann<u></u><u></u></pre>
                                              <pre>- legal department -<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Key-Systems GmbH<u></u><u></u></pre>
                                              <pre>Im Oberen Werk 1<u></u><u></u></pre>
                                              <pre>66386 St. Ingbert<u></u><u></u></pre>
                                              <pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><u></u><u></u></pre>
                                              <pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><u></u><u></u></pre>
                                              <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><u></u><u></u></pre>
                                              <pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<u></u><u></u></pre>
                                              <pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><u></u><u></u></pre>
                                              <pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>CEO: Alexander Siffrin<u></u><u></u></pre>
                                              <pre>Registration No.: HR B 18835 - Saarbruecken <u></u><u></u></pre>
                                              <pre>V.A.T. ID.: DE211006534<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>Member of the KEYDRIVE GROUP<u></u><u></u></pre>
                                              <pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre>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.<u></u><u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                              <pre><u></u> <u></u></pre>
                                            </div>
                                          </div>
                                        </div>
                                        <p class="MsoNormal">______________________________<wbr>_________________
                                          gnso-rds-pdp-wg mailing list <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
                                          <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a>
                                          <u></u><u></u></p>
                                      </blockquote>
                                    </div>
                                  </div>
                                  <pre>______________________________<wbr>_________________<u></u><u></u></pre>
                                  <pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
                                  <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
                                  <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
                                </blockquote>
                                <pre>-- <u></u><u></u></pre>
                                <pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Mit freundlichen Grüßen,<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Volker A. Greimann<u></u><u></u></pre>
                                <pre>- Rechtsabteilung -<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Key-Systems GmbH<u></u><u></u></pre>
                                <pre>Im Oberen Werk 1<u></u><u></u></pre>
                                <pre>66386 St. Ingbert<u></u><u></u></pre>
                                <pre>Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a><u></u><u></u></pre>
                                <pre>Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a><u></u><u></u></pre>
                                <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><u></u><u></u></pre>
                                <pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<u></u><u></u></pre>
                                <pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><u></u><u></u></pre>
                                <pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Geschäftsführer: Alexander Siffrin<u></u><u></u></pre>
                                <pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <u></u><u></u></pre>
                                <pre>Umsatzsteuer ID.: DE211006534<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Member of the KEYDRIVE GROUP<u></u><u></u></pre>
                                <pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>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.<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>------------------------------<wbr>--------------<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Should you have any further questions, please do not hesitate to contact us.<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Best regards,<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Volker A. Greimann<u></u><u></u></pre>
                                <pre>- legal department -<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Key-Systems GmbH<u></u><u></u></pre>
                                <pre>Im Oberen Werk 1<u></u><u></u></pre>
                                <pre>66386 St. Ingbert<u></u><u></u></pre>
                                <pre>Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a><u></u><u></u></pre>
                                <pre>Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a><u></u><u></u></pre>
                                <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><u></u><u></u></pre>
                                <pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<u></u><u></u></pre>
                                <pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><u></u><u></u></pre>
                                <pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>CEO: Alexander Siffrin<u></u><u></u></pre>
                                <pre>Registration No.: HR B 18835 - Saarbruecken <u></u><u></u></pre>
                                <pre>V.A.T. ID.: DE211006534<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>Member of the KEYDRIVE GROUP<u></u><u></u></pre>
                                <pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>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.<u></u><u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre><u></u> <u></u></pre>
                                <pre>______________________________<wbr>_________________<u></u><u></u></pre>
                                <pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
                                <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
                                <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
                              </blockquote>
                            </div>
                            <br>
                            <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
                            <br>
                            <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
                          </blockquote>
                          <br>
                          <pre class="m_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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>
                      </blockquote>
                      <blockquote type="cite">
                        <div><span>______________________________<wbr>_________________</span><br>
                          <span>gnso-rds-pdp-wg mailing list</span><br>
                          <span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br>
                          <span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
                      </blockquote>
                      <br>
                      <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
                      <br>
                      <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
                    </blockquote>
                    <br>
                  </div>
                </blockquote>
                <br>
                <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
              </blockquote>
              <br>
            </div>
          </blockquote>
          <blockquote type="cite">
            <div><span>______________________________<wbr>_________________</span><br>
              <span>gnso-rds-pdp-wg mailing list</span><br>
              <span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br>
              <span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
          </blockquote>
          <br>
          <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
          <br>
          <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
        </blockquote>
        <br>
        <pre class="m_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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>
        <br>
        <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
        <br>
        <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
      </blockquote>
      <br>
      <pre class="m_-4716820262215756001moz-signature" cols="72">-- 
--

John Bambenek</pre>
      <br>
      <fieldset class="m_-4716820262215756001mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-4716820262215756001moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
    </blockquote>
    <br>
    <pre class="m_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>

Web: <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-4716820262215756001moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-4716820262215756001moz-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_-4716820262215756001moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-4716820262215756001moz-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_-4716820262215756001moz-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></div></div>

<br>______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">_________________________________<br>Note to self: Pillage BEFORE burning.</div>
</div>