<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I think we should not get down to whataboutism and focus on our
      own topics.</p>
    <p>Volker</p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 26.09.2017 um 18:21 schrieb allison
      nixon:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACLR7w+jnOatY_0bLuBixmsQ7+C+_-dziJRiRA-4Kt7SytjWpQ@mail.gmail.com">
      <div dir="ltr">Can someone clearly and plainly explain why social
        media exposure is permissible but whois is not, given that both
        have privacy settings that can be invoked
        <div><br>
        </div>
        <div>there is no logical consistency for why social media is
          fine as-is but whois must be locked down. This only makes
          sense logically if the privacy controls youall offer to your
          customers are broken and do not legally qualify as obtaining
          consent. so please explain</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Sep 26, 2017 at 12:13 PM,
          Dotzero <span dir="ltr">&lt;<a
              href="mailto:dotzero@gmail.com" target="_blank"
              moz-do-not-send="true">dotzero@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">
              <div>You are raising a different discussion/issue Andrew.
                A discussion of what the working group thinks is
                appropriate is a different discussion vs assertions as
                to the legal requirements from various jurisdictions as
                to what we are obliged to do.<br>
                <br>
                I keep on hearing law invoked and therefore asked what
                precedent there is specific to whois and CBDF. It's a
                straight forward question and with the various privacy
                and legal experts on the list, one that should be easily
                answered if there are precedents specific to whois out
                there. Volker threw up a laundry list of references that
                don't really apply to the question I asked.  <br>
                <br>
              </div>
              Michael Hammer<br>
              <div class="gmail_extra"><br>
                <div class="gmail_quote"><span class="">On Tue, Sep 26,
                    2017 at 11:12 AM, Andrew Sullivan <span dir="ltr">&lt;<a
                        href="mailto:ajs@anvilwalrusden.com"
                        target="_blank" moz-do-not-send="true">ajs@anvilwalrusden.com</a>&gt;</span>
                    wrote:<br>
                  </span>
                  <div>
                    <div class="h5">
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex"><span
                          class="m_1207958936456866203gmail-">On Tue,
                          Sep 26, 2017 at 10:59:15AM -0400, Dotzero
                          wrote:<br>
                          &gt; predecessor regulations have been around
                          for quite some time and if the<br>
                          &gt; whois privacy issues we have been
                          debating are truly a significant problem<br>
                          &gt; to the extent that some represent them to
                          be, I would expect that there<br>
                          &gt; would have been at least some sort of
                          precedents specific to whois.<br>
                          <br>
                        </span>I think that, regardless of any legal
                        cases, the current whois leaks<br>
                        way too much information.  ICANN has an enormous
                        bureaucracy around<br>
                        "whois accuracy" partly (but only partly)
                        because ordinary people<br>
                        don't want to pay extra to keep their home
                        telephone numbers off from<br>
                        being wide open on the Internet, so they lie
                        about it.  There is _no<br>
                        reason_ that we are still using an ancient
                        protocol that was designed<br>
                        for a completely different network environment.<br>
                        <br>
                        The IAB recommends, in RFC 6973, that protocols
                        do something about<br>
                        data minimization (see section 6.1).  The
                        evidence we have is that<br>
                        greater exposure of data provides a vector for
                        attacks we haven't even<br>
                        thought about.  Therefore, we should not expose
                        data to everyone<br>
                        unless we are sure that it is necessary (and
                        some of this data _is_<br>
                        necessary to expose to everyone); and we should
                        be able to track who<br>
                        got the data if we're exposing data that is not
                        published to everyone.<br>
                        <br>
                        I don't think any of this should be news, and I
                        think it is really<br>
                        strange that we seem still to be discussing
                        whether it is something we<br>
                        need to embrace.<br>
                        <span class="m_1207958936456866203gmail-"><br>
                          Best regards,<br>
                          <br>
                          A<br>
                          <br>
                          <br>
                          --<br>
                          Andrew Sullivan<br>
                          <a href="mailto:ajs@anvilwalrusden.com"
                            target="_blank" moz-do-not-send="true">ajs@anvilwalrusden.com</a><br>
                          ______________________________<wbr>_________________<br>
                          gnso-rds-pdp-wg mailing list<br>
                          <a href="mailto:gnso-rds-pdp-wg@icann.org"
                            target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
                        </span><a
                          href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a><br>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <br>
              </div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            gnso-rds-pdp-wg mailing list<br>
            <a href="mailto:gnso-rds-pdp-wg@icann.org"
              moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
            <a
              href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
              rel="noreferrer" target="_blank" moz-do-not-send="true">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>
      <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>
  </body>
</html>