<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Susan,</p>
    <p>I still feel this is premature. Even if the rec is 6 years old,
      the PDP recommendations are still very fresh not even implemented
      yet. The GNSO council has approved them as has the board and a
      broad community consensus. <br>
    </p>
    <p>I also have an issue with your assumption that we know who our
      customer is. We don't. We never met most of them. Most of them do
      not even have an account with us and pay their direct provider
      instead. We cannot "ensure" accuracy anymore than we can "ensure"
      a winning lottery ticket. All we can ensure is that the data meets
      a certain format (validation) and either email or phone number
      (usually email) works at the time the domain is registered
      (verification). <br>
    </p>
    <p>To provide the data entrusted by the registrant to us to ICANN
      for anything but the agreed purpose would violate that trust. They
      certainly do not have a legitimate interest in that particular set
      of data that outweighs that particular registrants interest in
      privacy. </p>
    <p>Best,</p>
    <p>Volker<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 07.06.2018 um 19:20 schrieb Susan
      Kawaguchi:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJjzonEePEQJBQw26JmXHa1rimpOpYzG4bdA6CXy0aPLg=_EnQ@mail.gmail.com">
      <div dir="ltr">Hi Volker 
        <div><br>
        </div>
        <div>I disagree that our only option is to say thank you.  This
          recommendation is 6 years old so it would make sense that as
          an RT we would review the policy created by the PDP and make a
          recommendation in view of what has transpired in the last 6
          years. </div>
        <div><br>
        </div>
        <div>The Temp Spec addresses accuracy of data.  What is being
          recommended is that a registrar treat the underlying
          registrant data the same way it is required to validate
          registrant data now.  A registrar knows who their customer is
          and can ensure that the data under the PP is accurate without
          disclosing that to the world. </div>
        <div><br>
        </div>
        <div>Your claim this would violate the underlying registrant's
          privacy I do not follow that line of thinking at all. </div>
        <div><br>
        </div>
        <div>We should continue to discuss this recommendation. </div>
        <div><br>
        </div>
        <div>Susan </div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Jun 7, 2018 at 7:37 AM, Volker
          Greimann <span dir="ltr"><<a
              href="mailto:vgreimann@key-systems.net" target="_blank"
              moz-do-not-send="true">vgreimann@key-systems.net</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <p>I do not support any attempt to introduce an obligation
                for service providers to violate the privacy of their
                customers simply for purposes of "checks".</p>
              <p>The PPSAI WG has made very specific decisions regarding
                the obligations of service providers regarding data
                quality. It is not our place to question these decisions
                which have been approved by the GNSO and the board and
                are now on their final stretch of implementation. <br>
              </p>
              <p>Our report should only say: "thank you ICANN, job well
                done!"</p>
              <p>Anything beyond that is a job for the review of the
                policy after it has been implemented for a while.<br>
              </p>
              <p>Volker<br>
              </p>
              <br>
              <div class="m_-6839439845171155380moz-cite-prefix">Am
                06.06.2018 um 20:21 schrieb Carlton Samuels:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_default"
                    style="font-family:tahoma,sans-serif;font-size:large">Hi
                    Lili:<br>
                    See my comments in line.</div>
                  <div class="gmail_extra"><br clear="all">
                    <div>
                      <div class="m_-6839439845171155380gmail_signature"
                        data-smartmail="gmail_signature">
                        <div dir="ltr">
                          <div>
                            <div dir="ltr">
                              <div><br>
                                ==============================<br>
                                <i><font face="comic sans ms,
                                    sans-serif">Carlton A Samuels</font></i><br>
                                <font face="comic sans ms, sans-serif"><i>Mobile:
                                    876-818-1799<br>
                                    <font color="#33CC00">Strategy,
                                      Process, Governance, Assessment
                                      & Turnaround</font></i></font><br>
                                =============================</div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                    <br>
                    <div class="gmail_quote">On Sat, Jun 2, 2018 at
                      10:21 PM, SUN Lili <span dir="ltr"><<a
                          href="mailto:L.SUN@interpol.int"
                          target="_blank" moz-do-not-send="true">L.SUN@interpol.int</a>></span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div link="#0563C1" vlink="#954F72" lang="EN-SG">
                          <div
                            class="m_-6839439845171155380m_-5119598688317337846WordSection1">
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Dear
                                Privacy & Proxy subgroup members,</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I
                                went through the draft report of this
                                subgroup on wiki page (<a
                                  href="https://community.icann.org/pages/viewpage.action?pageId=71604717"
                                  target="_blank" moz-do-not-send="true">https://community.icann.org/p<wbr>ages/viewpage.action?pageId=71<wbr>604717</a>)
                                and step in with my concerns:</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span>1.<span
                                    style="font:7.0pt "Times New
                                    Roman"">       </span></span></span><span
                                dir="LTR"></span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">To
                                the Data Accuracy subgroup, the Whois
                                accuracy of domain names that utilize
                                Privacy and Proxy Services is invisible.
                                And Volker also mentioned that this will
                                be dealt with in the Privacy & Proxy
                                subgroup. </span></p>
                          </div>
                        </div>
                      </blockquote>
                      <div>
                        <div class="gmail_default"
                          style="font-family:tahoma,sans-serif;font-size:large;display:inline">​Under
                          current rules, the accredited P/P provider is
                          obliged to ensure contactability of customer
                          of his service​. That this is the case cannot
                          be verified independently and some of us have
                          argued from inception this is a major hole in
                          the agreement. We have alternately argued that
                          there should be graded penalties for this
                          violation after the fact.</div>
                      </div>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div link="#0563C1" vlink="#954F72" lang="EN-SG">
                          <div
                            class="m_-6839439845171155380m_-5119598688317337846WordSection1">
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">As
                                such, I strongly support Susan’s
                                comments on “6 Conducting periodic due
                                diligence checks on customer contact
                                information” and “8 Providing clear and
                                unambiguous guidance on the rights and
                                responsibilities of registered name
                                holders, and how those should be managed
                                in the privacy/proxy environment.” There
                                is no reason for a customer who chose
                                P/P service thus been protected from
                                responsibilities.</span></p>
                          </div>
                        </div>
                      </blockquote>
                      <div>
                        <div class="gmail_default"
                          style="font-family:tahoma,sans-serif;font-size:large;display:inline">​See
                          above. We expect that the risk triage will
                          allow the cost of violation to pass to the
                          customer.​</div>
                         </div>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div link="#0563C1" vlink="#954F72" lang="EN-SG">
                          <div
                            class="m_-6839439845171155380m_-5119598688317337846WordSection1">
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"></span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span>2.<span
                                    style="font:7.0pt "Times New
                                    Roman"">       </span></span></span><span
                                dir="LTR"></span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">There
                                is no indication about the legacy domain
                                names that utilize P/P Services before
                                the provider been accredited. Will it be
                                a similar situation as Grandfathered
                                domains?</span></p>
                          </div>
                        </div>
                      </blockquote>
                      <div>
                        <div class="gmail_default"
                          style="font-family:tahoma,sans-serif;font-size:large;display:inline">​Some
                          of us have argued that there should be a
                          Privacy/Proxy Data Accuracy Reminder policy
                          along the line of the WHOIS Data reminder. It
                          was not accepted. But there is no reason the
                          P/P provider cannot be obliged and bound to it
                          in terms of the accreditation for renewals. ​</div>
                         </div>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div link="#0563C1" vlink="#954F72" lang="EN-SG">
                          <div
                            class="m_-6839439845171155380m_-5119598688317337846WordSection1">
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"></span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <p
                              class="m_-6839439845171155380m_-5119598688317337846MsoListParagraph"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span>3.<span
                                    style="font:7.0pt "Times New
                                    Roman"">       </span></span></span><span
                                dir="LTR"></span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Like
                                the example I gave during the 2<sup>nd</sup>
                                F2F meeting, if there is not enough
                                regulation and overseeing in place, P/P
                                service is very likely to be abused. To
                                be clear, I elaborated the example in a
                                word document (see attached). Do we
                                really need this kind of fake prosperity
                                of domain industry?</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">A
                                response from this subgroup is much
                                appreciated.</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                          </div>
                        </div>
                      </blockquote>
                      <div>
                        <div class="gmail_default"
                          style="font-family:tahoma,sans-serif;font-size:large;display:inline">​Best,</div>
                      </div>
                      <div>
                        <div class="gmail_default"
                          style="font-family:tahoma,sans-serif;font-size:large;display:inline">-Carlton​</div>
                         </div>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div link="#0563C1" vlink="#954F72" lang="EN-SG">
                          <div
                            class="m_-6839439845171155380m_-5119598688317337846WordSection1">
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"></span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thanks,</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Lili</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
                            <div>
                              <p class="MsoNormal"> </p>
                            </div>
                          </div>
                          <div> ******************************<wbr>******************************<wbr>******************************<wbr>*********<br>
                            This message, and any attachment contained,
                            are confidential and subject of legal
                            privilege. It may be used solely for the
                            designated police/justice purpose and by the
                            individual or entity to whom it is
                            addressed. The information is not to be
                            disseminated to another agency or third
                            party without the author’s consent, and must
                            not be retained longer than is necessary for
                            the fulfilment of the purpose for which the
                            information is to be used. All practicable
                            steps shall be taken by the recipients to
                            ensure that information is protected against
                            unauthorised access or processing. INTERPOL
                            reserves the right to enquire about the use
                            of the information provided.<br>
                            If you are not the intended recipient, be
                            advised that you have received this message
                            in error. In such a case, you should not
                            print it, copy it, make any use of it or
                            disclose it, but please notify us
                            immediately and delete the message from any
                            computer.<br>
                            ******************************<wbr>******************************<wbr>******************************<wbr>*******<br>
                          </div>
                        </div>
                        <br>
                        ______________________________<wbr>_________________<br>
                        RDS-WHOIS2-RT mailing list<br>
                        <a href="mailto:RDS-WHOIS2-RT@icann.org"
                          target="_blank" moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a><br>
                        <a
                          href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">https://mm.icann.org/mailman/l<wbr>istinfo/rds-whois2-rt</a><br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </div>
                <br>
                <fieldset
                  class="m_-6839439845171155380mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
RDS-WHOIS2-RT mailing list
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank" moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a>
<a class="m_-6839439845171155380moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/rds-whois2-rt</a>
</pre>
              </blockquote>
              <br>
              <pre class="m_-6839439845171155380moz-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="m_-6839439845171155380moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a>

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" 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="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" 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.

------------------------------<wbr>--------------

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

Best regards,

Volker A. Greimann
- legal department -

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

Web: <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" 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="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" 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="m_-6839439845171155380moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" 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>
            <br>
            ______________________________<wbr>_________________<br>
            RDS-WHOIS2-RT mailing list<br>
            <a href="mailto:RDS-WHOIS2-RT@icann.org"
              moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a><br>
            <a
              href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/rds-whois2-rt</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </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>