<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Well, isn't that going out the door soon anyway when the IANA
    function is released?<br>
    <br>
    Also note that there is no single unified whois policy. All this
    states is that there must be <span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">"public
      access to accurate and complete </span><abbr title="WHOIS
      (pronounced &quot;who is&quot;; not an acronym)"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">WHOIS </abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">information,
      including registrant, technical, billing, and administrative
      contact information"</span>. <br>
    <br>
    Nowhere does it state that the registrant may not avail himself of
    agents to fulfill this requirement for him. And nowhere does it
    state that this agent must reveal his customers data.<br>
    <br>
    Best,<br>
    <br>
    Volker<br>
    <br>
    <div class="moz-cite-prefix">Am 04.03.2015 um 06:07 schrieb Terri
      Stumme:<br>
    </div>
    <blockquote
cite="mid:CAGvh5H4UswCGXZOjevCMukGNdxQutz5uVCskqQaVjCYAvN6NTA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:georgia,serif;font-size:small">While this
          is true, we cannot ignore the Affirmation of Commitments:</div>
        <div class="gmail_default"
          style="font-family:georgia,serif;font-size:small"><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">9.3.1 </span><abbr
            title="Internet Corporation for Assigned Names and Numbers"
            class=""
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">ICANN</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px"> additionally
            commits to enforcing its existing policy relating to </span><abbr
            title="WHOIS (pronounced &quot;who is&quot;; not an
            acronym)"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">WHOIS</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">,
            subject to applicable laws. Such existing policy requires
            that </span><abbr title="Internet Corporation for Assigned
            Names and Numbers"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">ICANN</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px"> implement
            measures to maintain timely, unrestricted and public access
            to accurate and complete </span><abbr title="WHOIS
            (pronounced &quot;who is&quot;; not an acronym)"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">WHOIS </abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">information,
            including registrant, technical, billing, and administrative
            contact information. One year from the effective date of
            this document and then no less frequently than every three
            years thereafter, </span><abbr title="Internet Corporation
            for Assigned Names and Numbers" class=""
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">ICANN</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px"> will
            organize a review of </span><abbr title="WHOIS (pronounced
            &quot;who is&quot;; not an acronym)"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">WHOIS</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px"> policy
            and its implementation to assess the extent to which </span><abbr
            title="WHOIS (pronounced &quot;who is&quot;; not an
            acronym)"
style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px">WHOIS</abbr><span
style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:20px;line-height:28px"> policy
            is effective and its implementation meets the legitimate
            needs of law enforcement and promotes consumer trust. </span><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Mar 3, 2015 at 11:13 PM,
          Stephanie Perrin <span dir="ltr">&lt;<a
              moz-do-not-send="true"
              href="mailto:stephanie.perrin@mail.utoronto.ca"
              target="_blank">stephanie.perrin@mail.utoronto.ca</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Further to our
              discussion this morning about the openness (or otherwise)
              of WHOIS, here is the quote I was referring to from the
              SSAC document 003, from 2003:<br>
              <div style="font-size:20px;font-family:sans-serif">In
                order for Whois data to be readily available it must be
                both accessible and usable by </div>
              <div style="font-size:20px;font-family:sans-serif">automatic
                tools. To be accessible the Whois protocol must be
                updated to support the </div>
              <big><big>recent shift in the architecture to separate the
                  functions of the registry and the registrar. </big></big>
              <div style="width:1019px;min-height:1319px">
                <div style="font-size:20px;font-family:sans-serif">This
                  shift has made it impractical to support searching and
                  frequently makes it difficult to </div>
                <div style="font-size:20px;font-family:sans-serif">find
                  Whois services. To be usable the data returned by
                  Whois services must in be a </div>
                <div style="font-size:20px;font-family:sans-serif">common
                  format. </div>
                <div style="font-size:20px;font-family:sans-serif"><b>However,
                    being accessible and usable must also protect a
                    registrant's privacy. Many </b></div>
                <div style="font-size:20px;font-family:sans-serif"><b>countries
                    require that personal information is protected but
                    in addition registrants may </b></div>
                <div style="font-size:20px;font-family:sans-serif"><b>wish
                    to discourage the unintended, undesirable, and
                    otherwise unwanted uses of their </b></div>
                <div style="font-size:20px;font-family:sans-serif"><b>Whois
                    data. In particular, it is widely believed that
                    Whois data is a source of email </b></div>
                <div style="font-size:20px;font-family:sans-serif"><b>addresses
                    for the distribution of spam. Methods must be
                    developed to discourage the </b></div>
                <div style="font-size:20px;font-family:sans-serif"><b>harvesting
                    or mining of Whois information</b>.<br>
                  <br>
                  I interpret this as support for the notion that there
                  have been reservations from parties other than civil <br>
                  society, with respect to the concept of all WHOIS data
                  being freely available, from the early days of ICANN.<span
                    class="HOEnZb"><font color="#888888"><br>
                      Stephanie Perrin<br>
                    </font></span></div>
              </div>
              <br>
            </div>
            <br>
            _______________________________________________<br>
            Gnso-ppsai-pdp-wg mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><br>
            <a moz-do-not-send="true"
              href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg"
              target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <div class="gmail_signature">
          <div dir="ltr"><font><span
                style="background-color:rgb(159,197,232)"><i>Terri
                  Stumme</i></span></font>
            <div><font><span style="background-color:rgb(159,197,232)"><i>Intellligence
                    Analyst</i></span></font></div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-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>