<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>It'll be free. You'll just add it in the cost of doing business and pass the costs down to all consumers. As long as its not an incremental line item, regulatory problem solved.&nbsp;<br><br>--<div>John Bambenek</div></div><div><br>On Sep 25, 2017, at 03:07, Volker Greimann &lt;<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  
  
    <p>With the new proposals for whois privacy provider accreditation
      currently in the works and the costs attached to that program both
      in aded requirements that have to be followed and the
      accreditation cost, this service will never be "free".&nbsp; <br>
    </p>
    <p>Volker<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 23.09.2017 um 15:47 schrieb John
      Bambenek via gnso-rds-pdp-wg:<br>
    </div>
    <blockquote type="cite" cite="mid:E14EA55B-9F88-4B44-AAE2-DCBFDDA29D2D@bambenekconsulting.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div>Is one of there ways of exploring how to resolve the issue
        including making whois privacy for free for individual
        registrants?<br>
        <br>
        --
        <div>John Bambenek</div>
      </div>
      <div><br>
        On Sep 22, 2017, at 21:06, Chuck &lt;<a href="mailto:consult@cgomes.com" moz-do-not-send="true">consult@cgomes.com</a>&gt;
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <meta http-equiv="Content-Type" content="text/html;
            charset=utf-8">
          <meta name="Generator" content="Microsoft Word 15 (filtered
            medium)">
          <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
          <style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Arial",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
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;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:"Arial",sans-serif;}
span.EmailStyle21
        {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:833301223;
        mso-list-type:hybrid;
        mso-list-template-ids:380771906 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
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">Without in any way detracting from the
              concern for ICANN transparency and the need for keeping
              our PDP informed, I think it is important for us to
              recognize a few things:<o:p></o:p></p>
            <ul style="margin-top:0in" type="disc">
              <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">The GDPR
                is set to go into effect in May 2018.<o:p></o:p></li>
              <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">While I
                am cautiously hopeful that the RDS PDP WG will improve
                progress in our work, there is no way we will be close
                to done by May 2018.<o:p></o:p></li>
              <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">In the
                meantime, contracted parties will be faced with some
                serious conflicts between the terms of their agreements
                with ICANN and the GDPR that could result in significant
                fines if they continue to comply with their ICANN
                agreements.<o:p></o:p></li>
              <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Therefore,
                it does not seem unreasonable for ICANN staff to be
                exploring ways to resolve this dilemma until policy work
                can be completed.<o:p></o:p></li>
            </ul>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
            <p class="MsoNormal">Chuck<o:p></o:p></p>
            <p class="MsoNormal"><a name="_MailEndCompose" moz-do-not-send="true"><o:p>&nbsp;</o:p></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>From:</b> <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>
                  [<a 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>Vayra, Fabricio (Perkins Coie)<br>
                  <b>Sent:</b> Friday, September 22, 2017 8:16 AM<br>
                  <b>To:</b> Andrew Sullivan &lt;<a href="mailto:ajs@anvilwalrusden.com" moz-do-not-send="true">ajs@anvilwalrusden.com</a>&gt;;
                  <a 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></p>
              </div>
            </div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">Appreciate this feedback, Andrew.&nbsp;
              Simply put, my concern is that these independent and
              misinformed conversations will result in bad decision
              making that will run counter to our efforts here in this
              duly-constituted PDP WG that is following the standard
              ICANN processes for developing policy -- if not render
              them useless altogether.&nbsp; Which in turn highlights my
              earlier comment that this side-show effort from ICANN runs
              counter to the bottom up / standard ICANN processes for
              developing policy.<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">Maybe it's just me making a mountain
              out of a molehill, but Stephanie echoing these concerns on
              the last call encouraged me to reach out to my fellow WG
              members to see if others share the concern and wanted to
              act on it.<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">Others? <o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">-----Original Message-----<br>
              From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>
              [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
              On Behalf Of Andrew Sullivan<br>
              Sent: Friday, September 22, 2017 11:09 AM<br>
              To: <a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
              Subject: Re: [gnso-rds-pdp-wg] ICANN
              Meetings/Conversations with Data Protection and Privacy
              Commissioners<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">Hi,<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">On Fri, Sep 22, 2017 at 02:51:44PM
              +0000, Vayra, Fabricio (Perkins Coie) wrote:<o:p></o:p></p>
            <p class="MsoPlainText">&gt; <o:p></o:p></p>
            <p class="MsoPlainText">&gt; I couldn’t agree more with
              Stephanie and find it incredible that ICANN, despite our
              ongoing efforts and the plethora of published community
              concerns, are continuing with the approach of rushing to
              discussions with Data Protection and Privacy Commissioners
              “half-cocked.”&nbsp; Putting aside the apparent widely shared
              view that this approach is misinformed and dangerous, it’s
              simply redundant of and does not take advantage of our
              work within this PDP process&nbsp; -- one could even say that
              it runs counter to the bottom up and community led
              initiative on RDS/WHOIS.<o:p></o:p></p>
            <p class="MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">I don't understand what the problem
              is supposed to be.&nbsp; We are a<o:p></o:p></p>
            <p class="MsoPlainText">duly-constituted PDP WG that is
              following the standard ICANN processes<o:p></o:p></p>
            <p class="MsoPlainText">for developing policy.&nbsp; If other
              parts of ICANN want to talk to data<o:p></o:p></p>
            <p class="MsoPlainText">protection and privacy
              commissioners, or activists in favour of<o:p></o:p></p>
            <p class="MsoPlainText">publishing all personal data
              available in the universe, or privacy<o:p></o:p></p>
            <p class="MsoPlainText">activists who think the DNS should
              be closed in favour of onion<o:p></o:p></p>
            <p class="MsoPlainText">routing, or the committee of the
              Present King of France and the Easter<o:p></o:p></p>
            <p class="MsoPlainText">Bunny, why should we care?&nbsp; In the
              event (for which I have diminshing<o:p></o:p></p>
            <p class="MsoPlainText">hope) that we publish a report that
              is actionable by the GNSO, the<o:p></o:p></p>
            <p class="MsoPlainText">ordinary ICANN policy mechanisms
              will grind forward no matter what<o:p></o:p></p>
            <p class="MsoPlainText">meetings people have had.<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">We can best contribute to that end,
              in my opinion, by focussing on<o:p></o:p></p>
            <p class="MsoPlainText">getting done the work that we are
              supposed to be doing, rather than<o:p></o:p></p>
            <p class="MsoPlainText">worrying about all the other things
              other people might be doing.&nbsp; By<o:p></o:p></p>
            <p class="MsoPlainText">concentrating on this and making
              some progress, we might even reduce<o:p></o:p></p>
            <p class="MsoPlainText">the temptation of others to second
              guess this process.&nbsp; At the rate we<o:p></o:p></p>
            <p class="MsoPlainText">are currently moving, we appear to
              be destined to deliver something<o:p></o:p></p>
            <p class="MsoPlainText">right after heat death of the
              universe, and I suggest that that pace<o:p></o:p></p>
            <p class="MsoPlainText">is partly because there is no issue
              on which people are willing to<o:p></o:p></p>
            <p class="MsoPlainText">focus, come to a clear conclusion,
              and then let that conclusion stand.<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">I therefore urge that we focus on
              our task and not make our job harder<o:p></o:p></p>
            <p class="MsoPlainText">than it already is by attending to
              outside distractions.<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">Best regards,<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">A<o:p></o:p></p>
            <p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
            <p class="MsoPlainText">-- <o:p></o:p></p>
            <p class="MsoPlainText">Andrew Sullivan<o:p></o:p></p>
            <p class="MsoPlainText"><a href="mailto:ajs@anvilwalrusden.com" moz-do-not-send="true"><span style="color:windowtext;text-decoration:none">ajs@anvilwalrusden.com</span></a><o:p></o:p></p>
            <p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
            <p class="MsoPlainText">gnso-rds-pdp-wg mailing list<o:p></o:p></p>
            <p class="MsoPlainText"><a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true"><span style="color:windowtext;text-decoration:none">gnso-rds-pdp-wg@icann.org</span></a><o:p></o:p></p>
            <p class="MsoPlainText"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&amp;d=DwIGaQ&amp;c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&amp;r=6lUxzkhJPN5qts-Nve5TYqxoGjP81z1kCvXgsmw-MiQ&amp;m=9eU57wIVscyGuvbIbm2BAi8LELlVrSQBl5k9N2YJxfQ&amp;s=EWf3FrLMoZXzDzHkrW30uyrwfH-GkQk1TGt5Jc2ndKs&amp;e" moz-do-not-send="true"><span style="color:windowtext;text-decoration:none">https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&amp;d=DwIGaQ&amp;c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&amp;r=6lUxzkhJPN5qts-Nve5TYqxoGjP81z1kCvXgsmw-MiQ&amp;m=9eU57wIVscyGuvbIbm2BAi8LELlVrSQBl5k9N2YJxfQ&amp;s=EWf3FrLMoZXzDzHkrW30uyrwfH-GkQk1TGt5Jc2ndKs&amp;e</span></a>=
              <o:p></o:p></p>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
            <div class="MsoNormal" style="text-align:center" align="center">
              <hr size="2" align="center" width="100%"></div>
            <p class="MsoNormal"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:gray"><br>
                NOTICE: This communication may contain privileged or
                other confidential information. If you have received it
                in error, please advise the sender by reply email and
                immediately delete the message and any attachments
                without copying or disclosing the contents. Thank you.</span><o:p></o:p></p>
          </div>
        </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">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>
    <pre class="moz-signature" cols="72">-- 
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

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

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>

Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken 
Umsatzsteuer ID.: DE211006534

Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a> 

Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.

--------------------------------------------

Should you have any further questions, please do not hesitate to contact us.

Best regards,

Volker A. Greimann
- legal department -

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

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>

Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>

CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken 
V.A.T. ID.: DE211006534

Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a> 

This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.



</pre>
  

</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">gnso-rds-pdp-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></body></html>