<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <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="moz-cite-prefix">On 2017-09-28 09:34, John Bambenek via
      gnso-rds-pdp-wg wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:C1915C9C-918B-48B1-BDD8-DA4930D704B5@bambenekconsulting.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div>Public data cannot, by definition, be breached. </div>
      <div id="AppleMailSignature"><br>
      </div>
      <div id="AppleMailSignature">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" moz-do-not-send="true">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="moz-cite-prefix">On 28-9-2017 15:19, John Bambenek
            via gnso-rds-pdp-wg wrote:<br>
          </div>
          <blockquote type="cite"
            cite="mid:86549063-FE91-4683-BE30-B9C98945FDEA@bambenekconsulting.com">
            <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"
                moz-do-not-send="true">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="moz-cite-prefix">Am 27.09.2017 um 20:05
                  schrieb Chuck:<br>
                </div>
                <blockquote type="cite"
                  cite="mid:037f01d337bb$47d7bf90$d7873eb0$@cgomes.com">
                  <meta name="Generator" content="Microsoft Word 15
                    (filtered medium)">
                  <style><!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Lucida Grande";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
span.hoenzb
        {mso-style-name:hoenzb;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1829514649;
        mso-list-template-ids:607791768;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
                  <div class="WordSection1">
                    <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><o:p></o:p></p>
                    <p class="MsoNormal"><span style="color:windowtext"> </span><o:p></o:p></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><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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 ("<b>ICANN</b>")
                        is to ensure the stable and secure operation of
                        the Internet's unique identifier systems as
                        described in this <u>Section 1.1(a)</u> (the "<b>Mission</b>").
                        Specifically, ICANN:</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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 ("<b>DNS</b>") and
                        coordinates the development and implementation
                        of policies concerning the registration of
                        second-level domain names in generic top-level
                        domains ("<b>gTLDs</b>"). In this role, ICANN's
                        scope is to coordinate the development and
                        implementation of policies:</span><o:p></o:p></p>
                    <p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt;text-indent:-.25in;mso-list:l0
                      level1 lfo1"><!--[if !supportLists]--><span
                        style="font-size:10.0pt;font-family:Symbol"><span
                          style="mso-list:Ignore">·<span
                            style="font:7.0pt &quot;Times New
                            Roman&quot;">         </span></span></span><!--[endif]--><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><o:p></o:p></p>
                    <p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt;text-indent:-.25in;mso-list:l0
                      level1 lfo1"><!--[if !supportLists]--><span
                        style="font-size:10.0pt;font-family:Symbol"><span
                          style="mso-list:Ignore">·<span
                            style="font:7.0pt &quot;Times New
                            Roman&quot;">         </span></span></span><!--[endif]--><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's unique names
                        systems.</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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's Mission.</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333"
                        lang="EN">. . .</span><span
                        style="color:windowtext">”</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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'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'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><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:13.0pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333"
                        lang="EN"> Chuck</span><o:p></o:p></p>
                    <p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
                    <p class="MsoNormal"><a name="_MailEndCompose"
                        moz-do-not-send="true"><span
                          style="color:windowtext"><o:p> </o:p></span></a></p>
                    <span style="mso-bookmark:_MailEndCompose"></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="moz-txt-link-abbreviated"
                              href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
                              moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>
                            [<a class="moz-txt-link-freetext"
                              href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
                              moz-do-not-send="true">mailto:gnso-rds-pdp-wg-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="moz-txt-link-abbreviated"
                              href="mailto:gnso-rds-pdp-wg@icann.org"
                              moz-do-not-send="true">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<o:p></o:p></span></p>
                      </div>
                    </div>
                    <p class="MsoNormal"><o:p> </o:p></p>
                    <p>Except that the domain name system is not YOUR
                      system, it is ICANN's who has a very clear mandate
                      for the security and stability of the internet.<o:p></o:p></p>
                    <p>The purpose is NOT letting registrants get
                      domains and helping registries get paid. It never
                      has been.<o:p></o:p></p>
                    <p class="MsoNormal"><o:p> </o:p></p>
                    <div>
                      <p class="MsoNormal">On 09/27/2017 09:52 AM,
                        Volker Greimann wrote:<o:p></o:p></p>
                    </div>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <p>Hi Greg,<o:p></o:p></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.<o:p></o:p></p>
                      <p>This is very easy to answer for registrars: "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.". I am
                        leaving out any contractual requirements, as
                        they do not matter for the registrars' own
                        purpose. These are external purposes that the
                        registrar would have to execute without having
                        an own, direct need for. <o:p></o:p></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. <o:p></o:p></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. <o:p></o:p></p>
                      <p>So our first question always must be the
                        following:<o:p></o:p></p>
                      <p>"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?"<o:p></o:p></p>
                      <p>This has to be the basis of any design decision
                        and any argument made in this group. <o:p></o:p></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.  <o:p></o:p></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.<o:p></o:p></p>
                      <p>I think with our initial "purpose definition"
                        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 "Do we need a Facebook contact in the RDS?"
                        and always be "What contacts are needed as bare
                        minimum to achieve needs X, Y, Z, ...". <o:p></o:p></p>
                      <p>Best,<o:p></o:p></p>
                      <p>Volker<o:p></o:p></p>
                      <p class="MsoNormal"><o:p> </o:p></p>
                      <div>
                        <p class="MsoNormal">Am 27.09.2017 um 16:00
                          schrieb Greg Shatan:<o:p></o:p></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 "data
                                controllers" 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 "needs" 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.)<o:p></o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="font-family:&quot;Verdana&quot;,sans-serif"><o:p> </o:p></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
                                "why does a particular
                                [registrar/registry] need WHOIS/RDS?"<o:p></o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="font-family:&quot;Verdana&quot;,sans-serif"><o:p> </o:p></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"><o:p></o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="font-family:&quot;Verdana&quot;,sans-serif"><o:p> </o:p></span></p>
                          </div>
                        </div>
                        <div>
                          <p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">vgreimann@key-systems.net</a>&gt;
                              wrote:<o:p></o:p></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...<o:p></o:p></p>
                                <p><span style="color:#888888">Volker<o:p></o:p></span></p>
                                <div>
                                  <div>
                                    <p class="MsoNormal"><o:p> </o:p></p>
                                    <div>
                                      <p class="MsoNormal">Am 26.09.2017
                                        um 20:48 schrieb John Bambenek
                                        via gnso-rds-pdp-wg:<o:p></o:p></p>
                                    </div>
                                  </div>
                                </div>
                                <blockquote
                                  style="margin-top:5.0pt;margin-bottom:5.0pt">
                                  <div>
                                    <div>
                                      <p>"<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><o:p></o:p></p>
                                      <p><span
                                          style="font-size:13.5pt;font-family:&quot;Lucida
                                          Grande&quot;,serif">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><o:p></o:p></p>
                                      <p><span
                                          style="font-size:13.5pt;font-family:&quot;Lucida
                                          Grande&quot;,serif">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><o:p></o:p></p>
                                      <p><span
                                          style="font-size:13.5pt;font-family:&quot;Lucida
                                          Grande&quot;,serif">I will
                                          loudly and vigorously argue
                                          that the path advocated will
                                          make the problem FAR worse and
                                          not better. Hopefully we don't
                                          get to the point where I have
                                          actual data to prove that.</span><o:p></o:p></p>
                                      <p class="MsoNormal"><o:p> </o:p></p>
                                      <div>
                                        <p class="MsoNormal">On
                                          9/26/2017 1:34 PM, Stephanie
                                          Perrin wrote:<o:p></o:p></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><o:p></o:p></p>
                                      </blockquote>
                                      <p class="MsoNormal"><br>
                                        <br>
                                        <o:p></o:p></p>
                                      <pre>-- <o:p></o:p></pre>
                                      <pre>--<o:p></o:p></pre>
                                      <pre><o:p> </o:p></pre>
                                      <pre>John Bambenek<o:p></o:p></pre>
                                      <p class="MsoNormal"><br>
                                        <br>
                                        <o:p></o:p></p>
                                    </div>
                                  </div>
                                  <pre>_______________________________________________<o:p></o:p></pre>
                                  <pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
                                  <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
                                  <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
                                </blockquote>
                                <div>
                                  <div>
                                    <pre>-- <o:p></o:p></pre>
                                    <pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Volker A. Greimann<o:p></o:p></pre>
                                    <pre>- Rechtsabteilung -<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Key-Systems GmbH<o:p></o:p></pre>
                                    <pre>Im Oberen Werk 1<o:p></o:p></pre>
                                    <pre>66386 St. Ingbert<o:p></o:p></pre>
                                    <pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
                                    <pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
                                    <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a><o:p></o:p></pre>
                                    <pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
                                    <pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
                                    <pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
                                    <pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
                                    <pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
                                    <pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
                                    <pre><o:p> </o:p></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.<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>--------------------------------------------<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Best regards,<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Volker A. Greimann<o:p></o:p></pre>
                                    <pre>- legal department -<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Key-Systems GmbH<o:p></o:p></pre>
                                    <pre>Im Oberen Werk 1<o:p></o:p></pre>
                                    <pre>66386 St. Ingbert<o:p></o:p></pre>
                                    <pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
                                    <pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
                                    <pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a><o:p></o:p></pre>
                                    <pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
                                    <pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
                                    <pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>CEO: Alexander Siffrin<o:p></o:p></pre>
                                    <pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
                                    <pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
                                    <pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
                                    <pre><o:p> </o:p></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.<o:p></o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                    <pre><o:p> </o:p></pre>
                                  </div>
                                </div>
                              </div>
                              <p class="MsoNormal">_______________________________________________
                                gnso-rds-pdp-wg mailing list <a
                                  href="mailto:gnso-rds-pdp-wg@icann.org"
                                  moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
                                <a
                                  href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
                                  target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a>
                                <o:p></o:p></p>
                            </blockquote>
                          </div>
                        </div>
                        <pre>_______________________________________________<o:p></o:p></pre>
                        <pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
                        <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
                        <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
                      </blockquote>
                      <pre>-- <o:p></o:p></pre>
                      <pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Volker A. Greimann<o:p></o:p></pre>
                      <pre>- Rechtsabteilung -<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Key-Systems GmbH<o:p></o:p></pre>
                      <pre>Im Oberen Werk 1<o:p></o:p></pre>
                      <pre>66386 St. Ingbert<o:p></o:p></pre>
                      <pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
                      <pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
                      <pre>Email: <a href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a><o:p></o:p></pre>
                      <pre><a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" moz-do-not-send="true">www.BrandShelter.com</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
                      <pre><a href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
                      <pre><a href="http://www.twitter.com/key_systems" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
                      <pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
                      <pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
                      <pre><a href="http://www.keydrive.lu" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
                      <pre><o:p> </o:p></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.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>--------------------------------------------<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Best regards,<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Volker A. Greimann<o:p></o:p></pre>
                      <pre>- legal department -<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Key-Systems GmbH<o:p></o:p></pre>
                      <pre>Im Oberen Werk 1<o:p></o:p></pre>
                      <pre>66386 St. Ingbert<o:p></o:p></pre>
                      <pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
                      <pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
                      <pre>Email: <a href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Web: <a href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a><o:p></o:p></pre>
                      <pre><a href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" moz-do-not-send="true">www.BrandShelter.com</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
                      <pre><a href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
                      <pre><a href="http://www.twitter.com/key_systems" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>CEO: Alexander Siffrin<o:p></o:p></pre>
                      <pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
                      <pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
                      <pre><a href="http://www.keydrive.lu" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
                      <pre><o:p> </o:p></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.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>_______________________________________________<o:p></o:p></pre>
                      <pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
                      <pre><a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
                      <pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
                    </blockquote>
                  </div>
                  <br>
                  <fieldset class="mimeAttachmentHeader"></fieldset>
                  <br>
                  <pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
                </blockquote>
                <br>
                <pre class="moz-signature" cols="72">-- 
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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 class="moz-txt-link-abbreviated" 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 class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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 class="moz-txt-link-abbreviated" 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>
              </div>
            </blockquote>
            <blockquote type="cite">
              <div><span>_______________________________________________</span><br>
                <span>gnso-rds-pdp-wg mailing list</span><br>
                <span><a href="mailto:gnso-rds-pdp-wg@icann.org"
                    moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></span><br>
                <span><a
                    href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
                    moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div>
            </blockquote>
            <br>
            <fieldset class="mimeAttachmentHeader"></fieldset>
            <br>
            <pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
          </blockquote>
          <br>
        </div>
      </blockquote>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
    </blockquote>
    <br>
  </body>
</html>